Triple

T21902863
Position Surface form Disambiguated ID Type / Status
Subject Lopik E540853 entity
Predicate hasBorderWith P224 FINISHED
Object Vijfheerenlanden 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: Vijfheerenlanden | Statement: [Lopik, hasBorderWith, Vijfheerenlanden]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vijfheerenlanden
Context triple: [Lopik, hasBorderWith, Vijfheerenlanden]
  • A. Vijfheerenlanden chosen
    Vijfheerenlanden is a historical region in the Netherlands known for its polder landscape and long-standing water management traditions along the Lek River.
  • B. Mijnsheerenland
    Mijnsheerenland is a village in the Dutch province of South Holland, known for its rural character and location on the island of Hoeksche Waard.
  • C. Koedijkslanden
    Koedijkslanden is a residential district in the Dutch city of Meppel, known for its suburban housing and local amenities.
  • D. Rietlanden
    Rietlanden is a waterfront area in Amsterdam’s Eastern Docklands, known for its former industrial port functions and subsequent urban redevelopment.
  • E. Foosland
    Foosland is a small village located in Champaign County, Illinois, United States.
  • 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_69e0c47b4e8c81908c8076eaa4c8e4f2 completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f121d3c23081908c30c3a617002389 completed April 28, 2026, 9:08 p.m.
Created at: April 16, 2026, 7:24 p.m.