Triple
T22330874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MCAS |
E552017
|
entity |
| Predicate | postAccidentChange |
P34334
|
FINISHED |
| Object | use of two angle of attack sensors for activation logic |
—
|
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: use of two angle of attack sensors for activation logic | Statement: [MCAS, postAccidentChange, use of two angle of attack sensors for activation logic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postAccidentChange Context triple: [MCAS, postAccidentChange, use of two angle of attack sensors for activation logic]
-
A.
hasAccidentAt
Indicates that an accident involving a subject occurs at a specific location or time.
-
B.
accident
Indicates an unintended, unforeseen event or mishap occurring, often resulting in damage, injury, or disruption.
-
C.
registrationStatusAfterAccident
Indicates the state of an entity’s registration following the occurrence of an accident.
-
D.
resultOfAccident
chosen
Indicates that something exists or occurs as a consequence or outcome of an accident.
-
E.
involvedInAccident
Indicates that an entity participated in, was affected by, or was otherwise a party to a specific accident or collision event.
- 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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1577a9c348190b8662142afa832be |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e73004d9e88190bb862319a5aea06b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:43 p.m.