Triple
T2726429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosetta mission |
E60203
|
entity |
| Predicate | missionEndEvent |
P39192
|
FINISHED |
| Object | controlled impact on comet 67P/Churyumov–Gerasimenko |
—
|
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: controlled impact on comet 67P/Churyumov–Gerasimenko | Statement: [Rosetta mission, missionEndEvent, controlled impact on comet 67P/Churyumov–Gerasimenko]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionEndEvent Context triple: [Rosetta mission, missionEndEvent, controlled impact on comet 67P/Churyumov–Gerasimenko]
-
A.
missionOutcome
Indicates the result or consequence of a mission, specifying whether and how the mission’s objectives were achieved or failed.
-
B.
finalMissionOf
Indicates that one entity is the last mission, assignment, or operation undertaken by another entity.
-
C.
reasonForEndOfMission
chosen
Indicates the cause or circumstance that led to the termination or conclusion of a mission.
-
D.
finalMissionPhase
Indicates that an entity is in, or corresponds to, the concluding or last phase of a mission.
-
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_69ab4b75cd908190b691ef0d1801acda |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdace9f308190964a064859612cd6 |
completed | March 7, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69abd82586f88190a98f60d3247fe2d3 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.