Triple
T16335844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gusev crater |
E396675
|
entity |
| Predicate | SpiritEndOfMissionLocation |
P81796
|
FINISHED |
| Object | Troy region in Gusev crater |
—
|
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: Troy region in Gusev crater | Statement: [Gusev crater, SpiritEndOfMissionLocation, Troy region in Gusev crater]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SpiritEndOfMissionLocation Context triple: [Gusev crater, SpiritEndOfMissionLocation, Troy region in Gusev crater]
-
A.
missionEnd
Indicates that a mission has concluded or reached its final state or outcome.
-
B.
formerFinishLocation
Indicates that an entity was previously the finish location of an event or activity, but no longer holds that status.
-
C.
finalMissionOf
Indicates that one entity is the last mission, assignment, or operation undertaken by another entity.
-
D.
climaxLocation
chosen
Indicates the place or setting where the most intense or pivotal moment of an event, narrative, or process occurs.
-
E.
reasonForEndOfMission
Indicates the cause or circumstance that led to the termination or conclusion of a mission.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2c4e3af7881908a3116c41ed69115 |
completed | April 17, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.