Triple

T5807475
Position Surface form Disambiguated ID Type / Status
Subject Achterhoek E128780 entity
Predicate borderWith P224 FINISHED
Object Twente E87641 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: Twente | Statement: [Achterhoek, borderWith, Twente]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Twente
Context triple: [Achterhoek, borderWith, 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. SC Heerenveen
    SC Heerenveen is a Dutch professional football club based in Heerenveen, known for competing in the Eredivisie and developing young talent.
  • D. AZ Alkmaar
    AZ Alkmaar is a Dutch professional football club based in Alkmaar, known for competing in the Eredivisie and developing talented players for top European leagues.
  • E. FC Eindhoven
    FC Eindhoven is a Dutch professional football club from Eindhoven that competes in the country’s league system and shares a historic city rivalry with PSV Eindhoven.
  • 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_69c0084788848190bcf71f6bc5d71597 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c02b17417081908779741b9bfbb720 completed March 22, 2026, 5:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69c0983ded9c8190b37372627c1e3a50 completed March 23, 2026, 1:32 a.m.
Created at: March 22, 2026, 3:52 p.m.