Triple
T23487070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deep Impact |
E570562
|
entity |
| Predicate | flybyClosestApproachDistance |
P59619
|
FINISHED |
| Object | about 500 kilometers from Tempel 1 |
—
|
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 500 kilometers from Tempel 1 | Statement: [Deep Impact, flybyClosestApproachDistance, about 500 kilometers from Tempel 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flybyClosestApproachDistance Context triple: [Deep Impact, flybyClosestApproachDistance, about 500 kilometers from Tempel 1]
-
A.
closestApproachDistance
chosen
Indicates the minimum distance between two entities at the point where they come closest to each other during their motion or interaction.
-
B.
distanceFromSunAtFlyby
Indicates the distance between an object and the Sun at the moment of its flyby event.
-
C.
flybyOrOrbiter
Indicates that one entity performs a close pass or maintains an orbital trajectory around another entity without landing on it.
-
D.
flybyOf
Indicates that one entity passes close to another in space without stopping, typically as part of an observational or transit maneuver.
-
E.
flybyDate
Indicates the date on which one object passes close to another in a flyby encounter.
- 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_69e245b0b01481908f636939bedd804c |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a754825481909b005ca5654c3159 |
completed | April 29, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:04 p.m.