Triple

T14918720
Position Surface form Disambiguated ID Type / Status
Subject Teuge Airport E371450 entity
Predicate near P350 FINISHED
Object Deventer NE NERFINISHED

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: Deventer | Statement: [Teuge Airport, near, Deventer]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Deventer
Context triple: [Teuge Airport, near, Deventer]
  • A. Deventer chosen
    Deventer is a historic Dutch city known for its medieval architecture, Hanseatic trading past, and annual book market.
  • B. Venlo
    Venlo is a historic city in the southeastern Netherlands, located near the German border on the river Meuse and known as a regional economic and logistics hub.
  • C. Hoorn
    Hoorn is a historic port city in the Netherlands known for its role in the Dutch Golden Age and as a former base of the Dutch East India Company.
  • D. Culemborg
    Culemborg is a historic town in the Dutch province of Gelderland, known for its medieval center and role in the early Dutch colonial era.
  • E. Valkenswaard
    Valkenswaard is a town in the southern Netherlands known for its strong equestrian culture and international show jumping events.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d85cc7ea3481908228b5acb7d06f12 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded62f76bc81909ebc8899096cd1a0 completed April 15, 2026, 12:05 a.m.
Created at: April 10, 2026, 2:33 a.m.