Triple
T5561172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arrokoth |
E145768
|
entity |
| Predicate | flybyDistance |
P59619
|
FINISHED |
| Object | about 3,500 kilometers |
—
|
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 3,500 kilometers | Statement: [Arrokoth, flybyDistance, about 3,500 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flybyDistance Context triple: [Arrokoth, flybyDistance, about 3,500 kilometers]
-
A.
flybyOf
Indicates that one entity passes close to another in space without stopping, typically as part of an observational or transit maneuver.
-
B.
closestApproachDistance
chosen
Indicates the minimum distance between two entities at the point where they come closest to each other during their motion or interaction.
-
C.
flybyDate
Indicates the date on which one object passes close to another in a flyby encounter.
-
D.
firstFlybyBy
Indicates that one entity was the spacecraft, probe, or mission that performed the first flyby of another entity (such as a celestial body or target).
-
E.
distanceFromEarth
Indicates the measured or calculated spatial separation between an entity and the planet Earth.
- 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_69c008fcaf788190bafa02a1917ee73b |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0201857848190a5443b51bcdb63fa |
completed | March 22, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69c01b10bbf8819098655839c03b7832 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:36 p.m.