Triple
T26629663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Earths in the Alpha Centauri Region |
E668456
|
entity |
| Predicate | distanceToTargets |
P120034
|
FINISHED |
| Object | approximately 4.37 light-years |
—
|
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: approximately 4.37 light-years | Statement: [New Earths in the Alpha Centauri Region, distanceToTargets, approximately 4.37 light-years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToTargets Context triple: [New Earths in the Alpha Centauri Region, distanceToTargets, approximately 4.37 light-years]
-
A.
distanceFromGoal
Indicates the measured or estimated separation between an entity’s current position and its intended goal or target state.
-
B.
distancesFrom
chosen
Indicates the measured spatial separation between one entity and one or more other entities.
-
C.
distanceToTerminal
Indicates the measured or calculated distance from a given entity or location to a specified terminal point or facility.
-
D.
distancedFrom
Indicates that one entity is physically or metaphorically kept at a certain distance or separation from another entity.
-
E.
distanceToWare
Indicates the measured distance between an entity and a specified ware or item.
- 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_69ee9cff507c819092b95bf7219a702e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69fe86cad5108190b0164b8bc6fc23ea |
completed | May 9, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69fe83c0c9888190b6fc40c7f727b569 |
completed | May 9, 2026, 12:45 a.m. |
Created at: April 27, 2026, 2:24 a.m.