Triple
T4885641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mariner 4 |
E109432
|
entity |
| Predicate | closestApproachDistance |
P59619
|
FINISHED |
| Object | about 9846 kilometers above Mars surface |
—
|
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 9846 kilometers above Mars surface | Statement: [Mariner 4, closestApproachDistance, about 9846 kilometers above Mars surface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closestApproachDistance Context triple: [Mariner 4, closestApproachDistance, about 9846 kilometers above Mars surface]
-
A.
closestApproachTarget
Indicates the entity that another entity comes nearest to during its path or motion.
-
B.
closestApproachDate
Indicates the date on which two entities come nearest to each other in space or position.
-
C.
closestApproachToPlutoDistance
Indicates the minimum distance an object comes to Pluto at the point of its closest approach.
-
D.
closestApproachToMoon
Indicates the point or distance at which an object comes nearest to the Moon along its trajectory or orbit.
-
E.
closestApproachDistanceToJupiter
Indicates the minimum distance an object comes to Jupiter during its trajectory or orbit.
- F. None of above. chosen
Provenance (4 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_69bd440f71348190b99938e59fb7f9a1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6de3718881908521968fa6e6b444 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2be5e881909f6ec9c3bcde49f3 |
completed | March 20, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69bd6d5976a081909090c0c263f6e9b7 |
completed | March 20, 2026, 3:52 p.m. |
Created at: March 20, 2026, 1:27 p.m.