Triple
T22923964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tucana dSph |
E569244
|
entity |
| Predicate | distanceFromAndromeda |
P7305
|
FINISHED |
| Object | comparable to its distance from the Milky Way |
—
|
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: comparable to its distance from the Milky Way | Statement: [Tucana dSph, distanceFromAndromeda, comparable to its distance from the Milky Way]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromAndromeda Context triple: [Tucana dSph, distanceFromAndromeda, comparable to its distance from the Milky Way]
-
A.
distanceToAndromedaGalaxy
chosen
Indicates the measured or calculated spatial distance between a given entity and the Andromeda Galaxy.
-
B.
positionRelativeToAndromeda
Indicates the spatial location or orientation of an entity in relation to the Andromeda galaxy.
-
C.
distanceFromM81
Indicates the measured or estimated spatial distance between an entity and the galaxy M81.
-
D.
distanceInMegaparsecs
Indicates the physical separation between two entities measured in units of megaparsecs.
-
E.
distanceFromMilkyWay
Indicates the measured or estimated spatial distance between an entity and the Milky Way galaxy.
- 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_69e2458f7d008190901dccbaebeaba24 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f180d7973c8190b09a5690fd1d3f28 |
completed | April 29, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69ef3b7c5fc081909ac50c5c8569cc19 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:43 p.m.