Triple
T36848028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mariner 1 |
E910603
|
entity |
| Predicate | timeFromLaunchToDestruction |
P56990
|
FINISHED |
| Object | about 293 seconds |
—
|
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 293 seconds | Statement: [Mariner 1, timeFromLaunchToDestruction, about 293 seconds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeFromLaunchToDestruction Context triple: [Mariner 1, timeFromLaunchToDestruction, about 293 seconds]
-
A.
timeOfDestruction
Indicates the specific time at which an entity is destroyed or ceases to exist.
-
B.
missionDurationFromLaunchToImpact
chosen
Indicates the total elapsed time between the launch of a mission and the moment of its impact.
-
C.
survivorsAtTimeOfDestruction
Indicates that the referenced entities were still alive or remained intact at the specific time when a particular destruction event occurred.
-
D.
timeOfMassExpulsion
Indicates the specific time at which a mass expulsion event occurs or is carried out.
-
E.
missionDuration
Indicates the length of time over which a mission or operation takes place from start to finish.
- 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_69f76e7f65a881908651b702da592b6d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.