Triple

T22153942
Position Surface form Disambiguated ID Type / Status
Subject Berkelland E547484 entity
Predicate hasSettlement P1068 FINISHED
Object Eibergen E1521841 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: Eibergen | Statement: [Berkelland, hasSettlement, Eibergen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Eibergen
Context triple: [Berkelland, hasSettlement, Eibergen]
  • A. Eibergen chosen
    Eibergen is a town in the Dutch province of Gelderland, historically an independent municipality before being incorporated into the larger municipality of Berkelland.
  • B. Ubbergen
    Ubbergen is a village in the Dutch province of Gelderland, known for its scenic, hilly landscape near Nijmegen and the German border.
  • C. Eemshaven
    Eemshaven is a major seaport and energy hub in the north of the Netherlands, known for its power plants, data centers, and offshore wind connections.
  • D. Bolsward
    Bolsward is a historic Frisian city in the Netherlands known for its well-preserved medieval center and canals.
  • E. Randaberg
    Randaberg is a coastal municipality in Rogaland county, Norway, situated just north of the city of Stavanger and known for its agriculture and scenic shoreline.
  • 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_69e11e3b52088190ad5df386d01eb2fb completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f129f6d5b88190badee2e515a3b633 completed April 28, 2026, 9:43 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0a9eb8d398819086031725209b6712 completed May 18, 2026, 5:08 a.m.
Created at: April 16, 2026, 8:33 p.m.