Triple
T13475534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 9M-MRO |
E318239
|
entity |
| Predicate | registrationStatusAfterDisappearance |
P67483
|
FINISHED |
| Object | cancelled |
—
|
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: cancelled | Statement: [9M-MRO, registrationStatusAfterDisappearance, cancelled]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registrationStatusAfterDisappearance Context triple: [9M-MRO, registrationStatusAfterDisappearance, cancelled]
-
A.
disappearanceStatus
Indicates the state or condition of whether and how something or someone has gone missing or ceased to be present.
-
B.
registrationStatus
chosen
Indicates the current state or condition of an entity’s enrollment or registration within a given system or process.
-
C.
disappearedDuring
Indicates that an entity ceased to be observable or present during the time span or event associated with another entity.
-
D.
timeOfDisappearance
Indicates the specific time at which an entity disappeared or was last observed to no longer be present.
-
E.
ceasedActivityUnder
Indicates that an entity stopped performing a particular activity while under the authority, influence, or conditions imposed by another entity.
- 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf2551b48190a074fd256791742d |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69dbadfddefc81909ef7fde23b181b5c |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:42 p.m.