Triple
T13475519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 9M-MRO |
E318239
|
entity |
| Predicate | incidentType |
P75088
|
FINISHED |
| Object | in-flight disappearance |
—
|
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: in-flight disappearance | Statement: [9M-MRO, incidentType, in-flight disappearance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: incidentType Context triple: [9M-MRO, incidentType, in-flight disappearance]
-
A.
notableIncidentType
Indicates the specific category or kind of significant event or incident associated with an entity.
-
B.
accidentType
Indicates the specific category or kind of accident associated with an event or incident.
-
C.
incidentCharacterization
chosen
Indicates how an incident is classified or characterized in terms of its nature, attributes, or type.
-
D.
accident
Indicates an unintended, unforeseen event or mishap occurring, often resulting in damage, injury, or disruption.
-
E.
resultOfAccident
Indicates that something exists or occurs as a consequence or outcome of an accident.
- 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.