Triple
T5060628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Messier 54 |
E114012
|
entity |
| Predicate | distanceFromSun_ly |
P2016
|
FINISHED |
| Object | 87000 |
—
|
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: 87000 | Statement: [Messier 54, distanceFromSun_ly, 87000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromSun_ly Context triple: [Messier 54, distanceFromSun_ly, 87000]
-
A.
approximateDistanceFromSun
Indicates an estimated or rough measure of how far an entity is from the Sun, rather than an exact distance.
-
B.
distanceFromSunCategory
Indicates the qualitative category or range into which an entity’s distance from the Sun falls (e.g., very close, moderate, far).
-
C.
hasMeanDistanceFromSun
chosen
Indicates that an entity (typically a celestial body) is characterized by a specific average distance from the Sun.
-
D.
distanceFromEarth
Indicates the measured or calculated spatial separation between an entity and the planet Earth.
-
E.
SunDistanceFromCenter
Indicates the distance between the Sun and the central reference point of a specified system (such as a galaxy or coordinate frame).
- 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_69bd443c0c8c81908663b77afb28e165 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7472a1dc8190942f568a81fdd961 |
completed | March 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69bd715622b48190a3e8e49a5ef62b4a |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:38 p.m.