Triple
T5246312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terzan 8 |
E118466
|
entity |
| Predicate | apparentPosition |
P9990
|
FINISHED |
| Object | direction of Sagittarius constellation |
—
|
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: direction of Sagittarius constellation | Statement: [Terzan 8, apparentPosition, direction of Sagittarius constellation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: apparentPosition Context triple: [Terzan 8, apparentPosition, direction of Sagittarius constellation]
-
A.
celestialLocation
chosen
Indicates the spatial or positional relationship of an entity relative to a celestial body or region in space.
-
B.
orbitReference
Indicates that one entity serves as the orbital frame, path, or reference system relative to which another entity’s orbit is defined or described.
-
C.
starPosition
Indicates the spatial location or coordinates of a star relative to a defined reference frame.
-
D.
solarPosition
Indicates the spatial orientation or location of an entity relative to the Sun at a given time.
-
E.
positionObtainedBy
Indicates that a particular position or role is acquired, achieved, or secured through a specified action, process, or agent.
- 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_69bd4468aacc8190a8196f71855cdf4f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b515edc8190a9db198d4eb1c4f6 |
completed | March 20, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69bd77c30bac8190a883ca45da35d667 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:49 p.m.