Triple

T6322529
Position Surface form Disambiguated ID Type / Status
Subject Leeuwarden E141776 entity
Predicate hasDemonym P191 FINISHED
Object Leeuwarder E141776 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: Leeuwarder | Statement: [Leeuwarden, hasDemonym, Leeuwarder]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Leeuwarder
Context triple: [Leeuwarden, hasDemonym, Leeuwarder]
  • A. Papendrecht
    Papendrecht is a Dutch town situated on the river Merwede in the province of South Holland, known for its residential character and proximity to the city of Dordrecht.
  • B. De Lier
    De Lier is a town and former municipality in the Dutch province of South Holland, known for its greenhouse horticulture and incorporation into the municipality of Westland.
  • C. Rolandswerth
    Rolandswerth is a district of the German town of Remagen, situated along the Rhine River in the state of Rhineland-Palatinate.
  • D. Leeuwarden chosen
    Leeuwarden is a historic city in the northern Netherlands, known as the capital of the province of Friesland and for its rich cultural and architectural heritage.
  • E. Venlo
    Venlo is a historic city in the southeastern Netherlands, located near the German border on the river Meuse and known as a regional economic and logistics hub.
  • 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_69c008d13b8c8190be47d896eb735605 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c064e38f1c81909c7e90b520602bae completed March 22, 2026, 9:53 p.m.
NED1 Entity disambiguation (via context triple) batch_69c6eec399f8819096e1db3ff6abd280 completed March 27, 2026, 8:55 p.m.
Created at: March 22, 2026, 4:29 p.m.