Triple

T33228246
Position Surface form Disambiguated ID Type / Status
Subject Embraer ERJ 140 E850616 entity
Predicate designedForAirlines P9494 FINISHED
Object regional airlines 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: regional airlines | Statement: [Embraer ERJ 140, designedForAirlines, regional airlines]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: designedForAirlines
Context triple: [Embraer ERJ 140, designedForAirlines, regional airlines]
  • A. designedForAirports
    Indicates that something is specifically created or optimized to be used in or meet the needs of airports.
  • B. designatedAirlineType
    Indicates that an airline has been assigned a specific operational or classification type for a given context or service.
  • C. designedAirGroup
    Indicates that one entity is the air group (aircraft complement or air wing) specifically planned or configured for use with another entity, such as a ship or platform.
  • D. eraOfDesignatedAircraft
    Indicates the historical time period or era during which the designated aircraft was primarily designed, developed, or in standard operational use.
  • E. isDesignedFor chosen
    Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of 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_69f349613f988190a1eb75467d167122 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69fe8ddf70e48190a917eb9e8f7b6966 completed May 9, 2026, 1:29 a.m.
PD Predicate disambiguation batch_69fe87ef94dc81909bb00ec8d6de9bcd completed May 9, 2026, 1:03 a.m.
Created at: May 1, 2026, 1:30 a.m.