Triple
T19901643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mariner 3 |
E478304
|
entity |
| Predicate | resultingTrajectory |
P137755
|
FINISHED |
| Object | failed to reach escape trajectory |
—
|
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: failed to reach escape trajectory | Statement: [Mariner 3, resultingTrajectory, failed to reach escape trajectory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultingTrajectory Context triple: [Mariner 3, resultingTrajectory, failed to reach escape trajectory]
-
A.
trajectoryAssist
Indicates assistance provided in planning, adjusting, or optimizing the path or course of motion of an entity.
-
B.
trajectoryType
Indicates the kind or pattern of motion an entity follows along its path over time.
-
C.
trajectoryCoverage
Indicates the extent to which a path or trajectory spans, visits, or accounts for the relevant space, time, or set of target points.
-
D.
payloadToEscapeTrajectory
Indicates that a payload is being directed onto a trajectory sufficient to escape the gravitational influence of a celestial body.
-
E.
trajectoryExpansion
Indicates how the path or course of something spreads, widens, or diversifies over time or space.
- 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_69d8e520682081909892916424699bd5 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65941977081909e2f94724eb2c3c0 |
completed | April 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69e537ecda248190895c96afb6243823 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c136b081909cab9394b958390a |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:52 p.m.