Triple

T23005925
Position Surface form Disambiguated ID Type / Status
Subject Made E572766 entity
Predicate hasNeighbouringSettlement P4647 FINISHED
Object Hooge Zwaluwe 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: Hooge Zwaluwe | Statement: [Made, hasNeighbouringSettlement, Hooge Zwaluwe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hooge Zwaluwe
Context triple: [Made, hasNeighbouringSettlement, Hooge Zwaluwe]
  • A. Krimpenerwaard
    Krimpenerwaard is a rural municipality in the Dutch province of South Holland, known for its polder landscapes, dikes, and traditional villages between the rivers Lek and Hollandse IJssel.
  • B. Rijkevorsel
    Rijkevorsel is a municipality in the Antwerp province of Belgium, located in the historic Kempen (Campine) region.
  • C. Zwanenburgwal
    Zwanenburgwal is a historic canal and street in central Amsterdam, known for its picturesque views and cultural significance.
  • D. De Vliedberg
    De Vliedberg is a residential neighborhood located within the Dutch municipality of Hellevoetsluis in South Holland.
  • E. Zwartewaal chosen
    Zwartewaal is a small village in the western Netherlands, located in the province of South Holland.
  • 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_69e245b6a3ac81908087599eefe3e365 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f18356417881908c8d6ee56bdc85f5 completed April 29, 2026, 4:04 a.m.
Created at: April 17, 2026, 3:51 p.m.