Triple
T12809422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pioneer 4 |
E306230
|
entity |
| Predicate | closestApproachDistanceToMoon |
P24802
|
FINISHED |
| Object | approximately 60,000 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: approximately 60,000 kilometers | Statement: [Pioneer 4, closestApproachDistanceToMoon, approximately 60,000 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closestApproachDistanceToMoon Context triple: [Pioneer 4, closestApproachDistanceToMoon, approximately 60,000 kilometers]
-
A.
closestApproachToMoon
chosen
Indicates the point or distance at which an object comes nearest to the Moon along its trajectory or orbit.
-
B.
closestApproachDistance
Indicates the minimum distance between two entities at the point where they come closest to each other during their motion or interaction.
-
C.
averageEarthMoonDistance_km
Indicates the average distance, measured in kilometers, between Earth and the Moon.
-
D.
closestApproachTarget
Indicates the entity that another entity comes nearest to during its path or motion.
-
E.
averageEarthMoonDistance_au
Indicates the average distance between Earth and the Moon, expressed in astronomical units (au).
- 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_69d7bdf46c448190b1faa55aaacb6317 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e817598819080fdd61e9d61236e |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d9640ed7448190b276e7fab649f7d2 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:31 p.m.