Triple

T9043777
Position Surface form Disambiguated ID Type / Status
Subject Ruurlo E216703 entity
Predicate regionalLanguage P237 FINISHED
Object Achterhooks E14290 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: Achterhooks | Statement: [Ruurlo, regionalLanguage, Achterhooks]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Achterhooks
Context triple: [Ruurlo, regionalLanguage, Achterhooks]
  • A. Achterhooks chosen
    Achterhooks is a regional Low Saxon dialect spoken in the Achterhoek area of the eastern Netherlands.
  • B. Hoornaar
    Hoornaar is a village in the Dutch province of South Holland, known for its rural character and traditional polder landscape.
  • C. Huncke
    Huncke is the surname of Herbert Huncke, an influential American writer and key figure of the Beat Generation whose life and stories deeply impacted authors like Jack Kerouac and William S. Burroughs.
  • D. Overhoeks
    Overhoeks is a modern waterfront district in Amsterdam known for its contemporary architecture, cultural venues, and redevelopment of former industrial land along the IJ river.
  • E. Hanzelijn
    Hanzelijn is a Dutch railway line connecting Lelystad and Zwolle, designed to shorten travel times between the Randstad and the northern Netherlands and partially built for higher-speed services.
  • 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_69ca83d22d488190adbce5e020e9cd1d completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cc6b137cec8190bd1b812c10d9542a completed April 1, 2026, 12:47 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfeba4c5f48190b7fc85f2137dd93e completed April 3, 2026, 4:32 p.m.
Created at: March 30, 2026, 7:09 p.m.