Triple
T17131767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mars Global Surveyor |
E415734
|
entity |
| Predicate | missionDurationInMarsOrbit |
P53433
|
FINISHED |
| Object | about 9 years |
—
|
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 9 years | Statement: [Mars Global Surveyor, missionDurationInMarsOrbit, about 9 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionDurationInMarsOrbit Context triple: [Mars Global Surveyor, missionDurationInMarsOrbit, about 9 years]
-
A.
timeInOrbit_days
chosen
Indicates the number of days an object has spent in orbit around a celestial body.
-
B.
missionDurationPlanned
Indicates the length of time that a mission is scheduled or intended to last according to its plan.
-
C.
missionDuration
Indicates the length of time over which a mission or operation takes place from start to finish.
-
D.
missionDurationFromLaunchToImpact
Indicates the total elapsed time between the launch of a mission and the moment of its impact.
-
E.
actualMissionDurationOnSurface
Indicates the length of time that a mission actually spent on the surface, as opposed to planned or total mission duration.
- 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f02a9fbc81909d820d29417aa55c |
completed | April 18, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69e3830192ac819091344a9e5a36c8c9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.