Triple
T32864775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Airways Flight 9 volcanic ash encounter |
E840618
|
entity |
| Predicate | engineStatus |
P128361
|
FINISHED |
| Object | flameout of all four engines |
—
|
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: flameout of all four engines | Statement: [British Airways Flight 9 volcanic ash encounter, engineStatus, flameout of all four engines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineStatus Context triple: [British Airways Flight 9 volcanic ash encounter, engineStatus, flameout of all four engines]
-
A.
operatorStatus
Indicates the current operational state or condition of an operator (e.g., active, inactive, or in error).
-
B.
operatingStatus
Indicates whether an entity is currently functioning, active, or in service versus inactive, closed, or out of service.
-
C.
driverStatus
Indicates the current operational or availability state of a driver in relation to their driving duties.
-
D.
automationStatus
Indicates whether a process, task, or system is being performed automatically or requires manual intervention.
-
E.
runtimeStatus
chosen
Indicates the current operational state or condition of an entity while it is running or executing.
- 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_69f34942465c819099b3fb47f9044f58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:17 a.m.