Triple
T5541458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sterope I |
E145298
|
entity |
| Predicate | isInNorthernCelestialHemisphere |
P65285
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Sterope I, isInNorthernCelestialHemisphere, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInNorthernCelestialHemisphere Context triple: [Sterope I, isInNorthernCelestialHemisphere, yes]
-
A.
locatedInNorthernHemisphere
Indicates that the subject is geographically situated in the Northern Hemisphere of the Earth.
-
B.
locatedInTheNorthernHemisphere
Indicates that the subject entity is situated geographically within the northern half of the Earth, above the equator.
-
C.
isCircumpolar
Indicates that an astronomical object remains perpetually above the horizon from a given observation point, never setting below it.
-
D.
visibleInHemisphere
Indicates that an object or phenomenon can be seen or observed from a specified hemisphere of a celestial body.
-
E.
visibleFromLatitudeNorth
Indicates that something can be seen or observed from locations at or north of a specified latitude.
- 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_69c008fa64888190adae56c8f9ea4031 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01fc66cc08190b9b2a62098ecbdb1 |
completed | March 22, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69c01b0e72f08190bf705d8fe1639401 |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f051e508190b3886d87b4afdd0b |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:35 p.m.