Triple

T16988189
Position Surface form Disambiguated ID Type / Status
Subject Automatic Warning System E412123 entity
Predicate consequenceOfNoAction P812 FINISHED
Object automatic full brake application 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: automatic full brake application | Statement: [Automatic Warning System, consequenceOfNoAction, automatic full brake application]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: consequenceOfNoAction
Context triple: [Automatic Warning System, consequenceOfNoAction, automatic full brake application]
  • A. consequenceOfChildlessness
    Indicates a condition, event, or outcome that arises specifically as a result of being childless.
  • B. consequenceOfDestruction
    Indicates that one event, state, or condition occurs as a direct result of a prior act of destruction.
  • C. hasConsequence chosen
    Indicates that one event, action, or condition leads to or results in another as its outcome or effect.
  • D. consequenceOfApplication
    Indicates that something occurs as a result or outcome of a particular application or use of something.
  • E. announcedConsequence
    Indicates that one entity has publicly stated or declared a specific outcome or consequence that will result from an action, event, 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_69d886ca8f348190812768ea8d5055ce completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3d27cd2048190800a60ae653e11e1 completed April 18, 2026, 6:50 p.m.
PD Predicate disambiguation batch_69e35d4dff4881909b384e30f2d36bff completed April 18, 2026, 10:30 a.m.
Created at: April 10, 2026, 5:32 a.m.