Triple

T22155149
Position Surface form Disambiguated ID Type / Status
Subject Sallandse Heuvelrug E547515 entity
Predicate near P350 FINISHED
Object Twente 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: Twente | Statement: [Sallandse Heuvelrug, near, Twente]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Twente
Context triple: [Sallandse Heuvelrug, near, Twente]
  • A. Twente chosen
    Twente is a historical and cultural region in the eastern Netherlands known for its rural landscapes, industrial heritage, and cities such as Enschede and Hengelo.
  • B. FC Twente
    FC Twente is a professional football club from Enschede in the Netherlands, known for competing in the Eredivisie and winning the Dutch league title in 2010.
  • C. De Graafschap
    De Graafschap is a professional Dutch football club based in Doetinchem, known for its passionate fanbase and history of competing in the Eredivisie and Eerste Divisie.
  • D. SC Heerenveen
    SC Heerenveen is a Dutch professional football club based in Heerenveen, known for competing in the Eredivisie and developing young talent.
  • E. SV Apeldoorn
    SV Apeldoorn is a Dutch sports club based in the city of Apeldoorn, primarily known for its football activities.
  • 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_69e11e3b52088190ad5df386d01eb2fb completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f129f7d034819092ecf9682e549c9a completed April 28, 2026, 9:43 p.m.
Created at: April 16, 2026, 8:33 p.m.