Triple
T21848168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galactic anticenter |
E539430
|
entity |
| Predicate | oppositeDirectionFromSun |
P116628
|
FINISHED |
| Object | Galactic center direction |
—
|
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: Galactic center direction | Statement: [Galactic anticenter, oppositeDirectionFromSun, Galactic center direction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oppositeDirectionFromSun Context triple: [Galactic anticenter, oppositeDirectionFromSun, Galactic center direction]
-
A.
directionFromSun
Indicates the orientation or bearing of an entity as measured outward from the Sun.
-
B.
directionFromEarth
Indicates the compass or spatial direction in which an entity is located as observed from Earth.
-
C.
visibilityRelativeToSun
Indicates how visible an entity is when considered in relation to the Sun’s position, brightness, or illumination conditions.
-
D.
viewDirectionAtSunrise
Indicates the direction an entity is oriented or looking toward at the time of sunrise.
-
E.
hasOppositeDirectionTo
chosen
Indicates that one entity’s direction is exactly reversed or opposed to the direction of another entity.
- 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_69e0c476c3c88190a92d08ebb59a128a |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0bd56f4e081909a906b64c1019e6a |
completed | April 28, 2026, 1:59 p.m. |
| PD | Predicate disambiguation | batch_69e6be8c14748190bdcc44a14d50bea4 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:55 p.m.