Triple
T4018009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mars Express |
E91209
|
entity |
| Predicate | missionExtended |
P8107
|
FINISHED |
| Object | multiple times beyond original nominal mission |
—
|
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: multiple times beyond original nominal mission | Statement: [Mars Express, missionExtended, multiple times beyond original nominal mission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionExtended Context triple: [Mars Express, missionExtended, multiple times beyond original nominal mission]
-
A.
missionExtension
chosen
Indicates that an existing mission is being prolonged beyond its originally planned duration or scope.
-
B.
missionEnd
Indicates that a mission has concluded or reached its final state or outcome.
-
C.
mission
Indicates that an entity is assigned or engaged in a specific task, operation, or purpose-directed undertaking.
-
D.
missionDuration
Indicates the length of time over which a mission or operation takes place from start to finish.
-
E.
missionStart
Indicates the point in time or event at which a mission or task officially begins.
- 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_69aed9618b04819081750d979d2af098 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaa984948190a252eaeb9dbae454 |
completed | March 9, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69aef8fc78ec819092d4dab88d85a141 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:35 p.m.