Triple
T23363882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1979 Air New Zealand Flight 901 crash |
E593257
|
entity |
| Predicate | crewErrorContext |
P144600
|
FINISHED |
| Object | unaware of changed flight path |
—
|
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: unaware of changed flight path | Statement: [1979 Air New Zealand Flight 901 crash, crewErrorContext, unaware of changed flight path]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewErrorContext Context triple: [1979 Air New Zealand Flight 901 crash, crewErrorContext, unaware of changed flight path]
-
A.
crewUser
Indicates that a user is a member of, or assigned as part of, a specific crew.
-
B.
crewNote
Indicates that a note or comment is recorded about a crew member or crew-related activity.
-
C.
crewTended
Indicates that a crew is responsible for attending to, operating, or maintaining something or someone.
-
D.
errorSide
chosen
Indicates the side, party, or component on which an error occurs or is attributed in a given context.
-
E.
crewOutcome
Indicates the result or status experienced by a crew as a consequence of an event, action, or condition.
- 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_69e25d2593c88190bcdf4a716a94ccb2 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a0aac4248190a4663ed12aed6856 |
completed | April 29, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:31 p.m.