Triple

T20009341
Position Surface form Disambiguated ID Type / Status
Subject Leeuwarden E494545 entity
Predicate hasHistoricName P2834 FINISHED
Object Leeuwaren NE NERFINISHED

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: Leeuwaren | Statement: [Leeuwarden, hasHistoricName, Leeuwaren]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Leeuwaren
Context triple: [Leeuwarden, hasHistoricName, Leeuwaren]
  • A. Leeuwaren chosen
    Leeuwaren (modern Dutch: Leeuwarden) is a historic city in the northern Netherlands that serves as the capital of the province of Friesland.
  • B. Wadenoijen
    Wadenoijen is a village in the Dutch province of Gelderland, located near the town of Tiel in the Betuwe region.
  • C. Houttuin
    Houttuin is a town in Suriname located within the Wanica District, known primarily as a residential and semi-rural community near the capital region.
  • D. Heezen
    Heezen is a surname most notably associated with American geologist and oceanographer Bruce C. Heezen, a pioneer in mapping the ocean floor.
  • E. Landsmeer
    Landsmeer is a small Dutch town and municipality in North Holland, situated just north of Amsterdam and known for its watery landscapes and nature reserves.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69da626b2d748190886981ea90c8b2ea completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e661a81c5881909692fcaaf59a57c9 completed April 20, 2026, 5:26 p.m.
Created at: April 11, 2026, 3:33 p.m.