Triple
T2402189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mars Orbiter Mission |
E47792
|
entity |
| Predicate | reasonForEndOfMission |
P39192
|
FINISHED |
| Object | loss of communication |
—
|
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: loss of communication | Statement: [Mars Orbiter Mission, reasonForEndOfMission, loss of communication]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForEndOfMission Context triple: [Mars Orbiter Mission, reasonForEndOfMission, loss of communication]
-
A.
finalMissionOf
Indicates that one entity is the last mission, assignment, or operation undertaken by another entity.
-
B.
reasonForEndOfTerm
Indicates the specific cause or circumstance that led to the termination or conclusion of a term, position, or period of service.
-
C.
finalMissionPhase
Indicates that an entity is in, or corresponds to, the concluding or last phase of a mission.
-
D.
reasonForExecution
Indicates that one entity specifies the cause, motive, or justification for carrying out the execution of another entity or action.
-
E.
reasonForRelease
Indicates the cause, justification, or circumstance that led to an entity being released.
- 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_69a88a1c450c81909f61abb8b6863885 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abceab9ce881909ae0a2f34515c11e |
completed | March 7, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69abc5a530e8819094105aa92dfaf6b3 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abceaa42b88190a790355100fede3d |
completed | March 7, 2026, 7:07 a.m. |
Created at: March 4, 2026, 7:57 p.m.