Triple

T1112535
Position Surface form Disambiguated ID Type / Status
Subject Limburgish (Dutch variety) E11026 entity
Predicate spokenIn P2266 FINISHED
Object Heerlen E453569 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: Heerlen | Statement: [Limburgish (Dutch variety), spokenIn, Heerlen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Heerlen
Context triple: [Limburgish (Dutch variety), spokenIn, Heerlen]
  • A. Heerlen chosen
    Heerlen is a city in the southeastern Netherlands known for its mining history and modernist architecture, located in the province of Limburg.
  • B. Gorinchem
    Gorinchem is a historic fortified city in the Netherlands known for its well-preserved city walls and picturesque old town.
  • C. Roermond
    Roermond is a historic city in the southeastern Netherlands known for its medieval architecture, prominent churches, and large designer outlet shopping center.
  • D. Eindhoven
    Eindhoven is a major city in the southern Netherlands known for its industrial and technological significance, particularly as a hub for electronics and design.
  • E. Apeldoorn
    Apeldoorn is a city in the province of Gelderland in the Netherlands, known for the royal palace Het Loo and its historical ties to the Dutch monarchy.
  • 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_69a493252a648190ac48f8742474a5e8 completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a4bb9ea0748190baaeadf76bacc3dd completed March 1, 2026, 10:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69befe34c0908190a618ff01ee27bfbb completed March 21, 2026, 8:23 p.m.
Created at: March 1, 2026, 7:43 p.m.