Triple

T22722338
Position Surface form Disambiguated ID Type / Status
Subject Maneuvering Characteristics Augmentation System E561894 entity
Predicate consequenceOfAccidents P34334 FINISHED
Object global grounding of Boeing 737 MAX fleet 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: global grounding of Boeing 737 MAX fleet | Statement: [Maneuvering Characteristics Augmentation System, consequenceOfAccidents, global grounding of Boeing 737 MAX fleet]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: consequenceOfAccidents
Context triple: [Maneuvering Characteristics Augmentation System, consequenceOfAccidents, global grounding of Boeing 737 MAX fleet]
  • A. resultOfAccident chosen
    Indicates that something exists or occurs as a consequence or outcome of an accident.
  • B. consequenceOfCollision
    Indicates that one event, state, or condition occurs as a direct result of a collision between entities.
  • C. causedAccident
    Indicates that one entity is responsible for bringing about or initiating an accident involving another entity or situation.
  • D. accident
    Indicates an unintended, unforeseen event or mishap occurring, often resulting in damage, injury, or disruption.
  • E. accidentType
    Indicates the specific category or kind of accident associated with an event or incident.
  • 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_69e2454fc984819088213b58ee87a002 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f17926ae0c8190af8493cab6b15261 completed April 29, 2026, 3:21 a.m.
PD Predicate disambiguation batch_69eed2a971c0819088af574e40c9343f completed April 27, 2026, 3:06 a.m.
Created at: April 17, 2026, 3:20 p.m.