Triple

T16818597
Position Surface form Disambiguated ID Type / Status
Subject Lyon–Saint-Exupéry Airport E408820 entity
Predicate serves P98 FINISHED
Object Lyon E15889 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: Lyon | Statement: [Lyon–Saint-Exupéry Airport, serves, Lyon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lyon
Context triple: [Lyon–Saint-Exupéry Airport, serves, Lyon]
  • A. Lyon
    Lyon is a historic Scottish noble family name most prominently associated with the Earls of Strathmore and Kinghorne.
  • B. Lyon chosen
    Lyon is a major city in east-central France known for its historical and architectural landmarks, gastronomy, and role as a key economic and cultural center.
  • C. Lyons
    Lyons is a small city in southeastern Georgia, United States, known as the administrative and commercial hub of Toombs County.
  • D. Lyons
    Lyons is a small town in northern Colorado known as a gateway to the Rocky Mountains and for its vibrant music and arts scene.
  • E. Lyons
    Lyons is a sports team or athletic program associated with Wheaton College, commonly referred to by this shortened name.
  • 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_69d88394566c8190b3dcbdc72935f7fa completed April 10, 2026, 4:59 a.m.
NER Named-entity recognition batch_69e3b2e476d48190bff097055cc353dc completed April 18, 2026, 4:35 p.m.
NED1 Entity disambiguation (via context triple) batch_6a014136275c819084da2756632e0f48 completed May 11, 2026, 2:38 a.m.
Created at: April 10, 2026, 5:23 a.m.