Triple
T18775898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sgr |
E459131
|
entity |
| Predicate | skyHemisphere |
P132944
|
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: [Sgr, skyHemisphere, southern celestial hemisphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: skyHemisphere Context triple: [Sgr, skyHemisphere, southern celestial hemisphere]
-
A.
visibleInHemisphere
Indicates that an object or phenomenon can be seen or observed from a specified hemisphere of a celestial body.
-
B.
skyQuality
Indicates the measured level or condition of the sky, typically in terms of clarity, brightness, or suitability for observation.
-
C.
skyTreatment
Indicates the method or process applied to alter, enhance, or manage the appearance or condition of the sky.
-
D.
isInNorthernCelestialHemisphere
Indicates that an astronomical object’s position lies north of the celestial equator in the northern half of the sky.
-
E.
visibleInEveningSky
Indicates that the entity can be seen in the sky during evening hours.
- F. None of above. chosen
Provenance (4 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5933ad4288190b17e5fad57d8417d |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d1126e4819099607837ed5aadca |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49785fd7081909577e90a55df0a35 |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:52 a.m.