Triple
T36705742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MOM camera |
E906354
|
entity |
| Predicate | statusOfHostMission |
P200834
|
FINISHED |
| Object | mission completed |
—
|
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: mission completed | Statement: [MOM camera, statusOfHostMission, mission completed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOfHostMission Context triple: [MOM camera, statusOfHostMission, mission completed]
-
A.
originalMissionStatus
Indicates the initial state or condition of a mission at the time it was first defined or launched.
-
B.
hostMissionPhase
Indicates that a host entity is associated with, or responsible for, a specific phase within a larger mission or operation.
-
C.
statusOfTarget
Indicates the current condition, state, or situation of the specified target entity.
-
D.
hostMissionCenter
Indicates that an entity serves as the location or organization that hosts, manages, or operates a mission center for another entity or activity.
-
E.
hostState
Indicates a relationship where one entity serves as the host or governing state for another entity, within whose jurisdiction, territory, or authority that other entity operates or resides.
- 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_69f76e7195c48190b5580c9cfb01e95f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffb1218cb08190a814c7f0833501a7 |
completed | May 9, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69ffb083d6988190b2757e0cfd629b75 |
completed | May 9, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69ffb120b9988190b6361c69265033c0 |
completed | May 9, 2026, 10:11 p.m. |
Created at: May 3, 2026, 4:12 p.m.