Triple

T34462677
Position Surface form Disambiguated ID Type / Status
Subject SurfaceWatch runway monitoring E884685 entity
Predicate alertsWhen P23340 FINISHED
Object aircraft is aligned with a runway different from the selected runway 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: aircraft is aligned with a runway different from the selected runway | Statement: [SurfaceWatch runway monitoring, alertsWhen, aircraft is aligned with a runway different from the selected runway]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: alertsWhen
Context triple: [SurfaceWatch runway monitoring, alertsWhen, aircraft is aligned with a runway different from the selected runway]
  • A. providesAlertsTo
    Indicates that one entity sends or delivers alerts or notifications to another entity.
  • B. alertSystem chosen
    Indicates that a system is configured to detect conditions and generate alerts or notifications in response.
  • C. alertMethod
    Indicates the method or channel through which an alert or notification is delivered from a source to a recipient.
  • D. notificationType
    Indicates the specific category or kind of notification associated with an event or action.
  • E. warningRecipient
    Indicates that one entity is the recipient or target audience of a warning issued by another entity.
  • 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_69f349c73a94819094dfcf50d00620b8 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f71996e1a48190ac59a1d66d7c44e8 completed May 3, 2026, 9:47 a.m.
PD Predicate disambiguation batch_69f71824431081908d9685d2462ea242 completed May 3, 2026, 9:40 a.m.
Created at: May 1, 2026, 2 a.m.