Triple
T4617918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Local Spur |
E100910
|
entity |
| Predicate | galacticRadiusApprox |
P7286
|
FINISHED |
| Object | about 8 kiloparsecs from Galactic Center |
—
|
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 8 kiloparsecs from Galactic Center | Statement: [Local Spur, galacticRadiusApprox, about 8 kiloparsecs from Galactic Center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: galacticRadiusApprox Context triple: [Local Spur, galacticRadiusApprox, about 8 kiloparsecs from Galactic Center]
-
A.
distanceFromGalacticCenter
chosen
Indicates the measured or calculated spatial separation between an entity and the center of its galaxy.
-
B.
distanceToGalacticCenter
Indicates the measured or calculated spatial distance between an entity and the center of its galaxy.
-
C.
positionRelativeToGalacticCenter
Indicates the spatial location of an entity expressed in relation to the center of its galaxy.
-
D.
approximateRadius
Indicates that one entity specifies or provides an estimated value for the radius of another entity.
-
E.
hostGalaxyDistanceEstimate
Indicates an estimated distance measurement between an astronomical object and its host 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59e247448190ad92f194cb1127c5 |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd522fd5c48190ad2bffc0a5bc9061 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.