Triple
T5129103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leo II Dwarf Galaxy |
E115651
|
entity |
| Predicate | distanceFromMilkyWayCenter |
P7286
|
FINISHED |
| Object | about 230 kiloparsecs |
—
|
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: about 230 kiloparsecs | Statement: [Leo II Dwarf Galaxy, distanceFromMilkyWayCenter, about 230 kiloparsecs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromMilkyWayCenter Context triple: [Leo II Dwarf Galaxy, distanceFromMilkyWayCenter, about 230 kiloparsecs]
-
A.
distanceFromMilkyWay
Indicates the measured or estimated spatial distance between an entity and the Milky Way galaxy.
-
B.
distanceFromMilkyWay_ly
Indicates the distance of an object from the Milky Way galaxy, measured in light-years.
-
C.
distanceFromGalacticCenter
chosen
Indicates the measured or calculated spatial separation between an entity and the center of its galaxy.
-
D.
distanceToGalacticCenter
Indicates the measured or calculated spatial distance between an entity and the center of its galaxy.
-
E.
distanceToEdgeFromMilkyWay
Indicates the measured or estimated distance from the Milky Way galaxy to the nearest edge or boundary of the referenced structure or region.
- 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_69bd444426bc819099ccd23f141e22aa |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7fef2e8c8190982dd67f50295ada |
completed | March 20, 2026, 5:12 p.m. |
| PD | Predicate disambiguation | batch_69bd77ac2fc48190abeebb003a82384c |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:42 p.m.