Triple

T9766270
Position Surface form Disambiguated ID Type / Status
Subject Betuwe E236999 entity
Predicate hasSubregion P285 FINISHED
Object Lingewaard
Lingewaard is a municipality in the Dutch province of Gelderland, situated in the Betuwe region between the cities of Arnhem and Nijmegen.
 E819290 NE FINISHED

How this triple was built (4 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: Lingewaard | Statement: [Betuwe, hasSubregion, Lingewaard]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Lingewaard
Context triple: [Betuwe, hasSubregion, Lingewaard]
  • A. Lingewaal
    Lingewaal was a former municipality in the Dutch province of Gelderland, known for encompassing several rural villages along the river Linge.
  • B. Goudswaard
    Goudswaard is a small village in the Dutch province of South Holland, known for its rural character and location on the island of Hoeksche Waard.
  • C. Zwanenburg
    Zwanenburg is a village in North Holland, Netherlands, situated near Amsterdam and known as a suburban residential community within the Haarlemmermeer municipality.
  • D. Weerde
    Weerde is a village in the Flemish Brabant province of Belgium, known as a residential suburb within the municipality of Zemst.
  • E. Zijdelwaard
    Zijdelwaard is a residential neighborhood in the town of Uithoorn in the province of North Holland, Netherlands.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Lingewaard
Triple: [Betuwe, hasSubregion, Lingewaard]
Generated description
Lingewaard is a municipality in the Dutch province of Gelderland, situated in the Betuwe region between the cities of Arnhem and Nijmegen.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: Lingewaard
Target entity description: Lingewaard is a municipality in the Dutch province of Gelderland, situated in the Betuwe region between the cities of Arnhem and Nijmegen.
  • A. Lingewaal
    Lingewaal was a former municipality in the Dutch province of Gelderland, known for encompassing several rural villages along the river Linge.
  • B. Goudswaard
    Goudswaard is a small village in the Dutch province of South Holland, known for its rural character and location on the island of Hoeksche Waard.
  • C. Zwanenburg
    Zwanenburg is a village in North Holland, Netherlands, situated near Amsterdam and known as a suburban residential community within the Haarlemmermeer municipality.
  • D. Weerde
    Weerde is a village in the Flemish Brabant province of Belgium, known as a residential suburb within the municipality of Zemst.
  • E. Zijdelwaard
    Zijdelwaard is a residential neighborhood in the town of Uithoorn in the province of North Holland, Netherlands.
  • F. None of above. chosen

Provenance (5 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_69ca84d831b8819090322686b47887ce completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cda0a15e408190909745cb1c30937d completed April 1, 2026, 10:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69d1bcf965e88190b505ce160f77e9b7 completed April 5, 2026, 1:38 a.m.
NEDg Description generation batch_69d1bd901e4881908a39be828eb7f21b completed April 5, 2026, 1:40 a.m.
NED2 Entity disambiguation (via description) batch_69d1bdfe40f4819096b1d0442f4ee181 completed April 5, 2026, 1:42 a.m.
Created at: March 30, 2026, 8:25 p.m.