Triple

T11204204
Position Surface form Disambiguated ID Type / Status
Subject TAP Express E265117 entity
Predicate fleetType P6198 FINISHED
Object Embraer 190 E11225 NE 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: Embraer 190 | Statement: [TAP Express, fleetType, Embraer 190]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Embraer 190
Context triple: [TAP Express, fleetType, Embraer 190]
  • A. Embraer 190 chosen
    The Embraer 190 is a Brazilian-made narrow-body regional jet airliner designed for short- to medium-haul routes, widely used by airlines around the world.
  • B. Embraer 175
    The Embraer 175 is a regional jet airliner designed for short- to medium-haul routes, widely used by airlines for its efficient performance and comfortable 70–88 seat cabin.
  • C. Embraer 195
    The Embraer 195 is a Brazilian-made regional jet airliner known for its short- to medium-haul efficiency and use by numerous carriers worldwide.
  • D. Embraer 170
    The Embraer 170 is a regional jet airliner designed and produced by Brazilian manufacturer Embraer, typically seating around 70 passengers for short- to medium-haul routes.
  • E. Embraer ERJ 145
    The Embraer ERJ 145 is a Brazilian-built regional jet airliner widely used for short-haul passenger and military transport operations.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d6aa9eb9248190b20211772621b4bc completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e8d355c481908fc3d555b596314d completed April 9, 2026, 5:58 p.m.
NED1 Entity disambiguation (via context triple) batch_69e4972bfbd481908cd0da59389ae17c completed April 19, 2026, 8:49 a.m.
Created at: April 8, 2026, 9:30 p.m.