Triple
T4959204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ascella |
E111361
|
entity |
| Predicate | skyPosition |
P9997
|
FINISHED |
| Object | southern celestial hemisphere |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: southern celestial hemisphere | Statement: [Ascella, skyPosition, southern celestial hemisphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: skyPosition Context triple: [Ascella, skyPosition, southern celestial hemisphere]
-
A.
celestialLocation
Indicates the spatial or positional relationship of an entity relative to a celestial body or region in space.
-
B.
starPosition
Indicates the spatial location or coordinates of a star relative to a defined reference frame.
-
C.
skyQuality
Indicates the measured level or condition of the sky, typically in terms of clarity, brightness, or suitability for observation.
-
D.
solarPosition
Indicates the spatial orientation or location of an entity relative to the Sun at a given time.
-
E.
locatedInSkyRegion
chosen
Indicates that an entity is situated within or associated with a specific region or area of the sky.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69bd4418390c8190b7e9766a2512ce55 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd72e49b048190bac55d9e7a6f7963 |
completed | March 20, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_69bd71447fe88190bb62c5e8753da7a7 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:32 p.m.