Triple

T5893392
Position Surface form Disambiguated ID Type / Status
Subject Loon op Zand E131043 entity
Predicate borderedBy P224 FINISHED
Object Gilze en Rijen E248162 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: Gilze en Rijen | Statement: [Loon op Zand, borderedBy, Gilze en Rijen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gilze en Rijen
Context triple: [Loon op Zand, borderedBy, Gilze en Rijen]
  • A. Gilze en Rijen chosen
    Gilze en Rijen is a municipality and town in the southern Netherlands known for its proximity to Breda and its military air base.
  • B. Land van Heusden
    Land van Heusden is a historic region in the northern part of the Dutch province of North Brabant, centered around the town of Heusden and known for its medieval fortifications and river landscapes.
  • C. Ridderkerk
    Ridderkerk is a town and municipality in the western Netherlands, situated near Rotterdam in the province of South Holland.
  • D. Soestdijk
    Soestdijk is a village in the Netherlands known for its historic royal residence, Soestdijk Palace.
  • E. Oosterwijtwerd
    Oosterwijtwerd is a small village in the province of Groningen in the northern Netherlands, known for its rural character and historic church.
  • 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_69c00857439c819095950754176aa58a completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c036b5c68481909fdcba428238c74d completed March 22, 2026, 6:36 p.m.
NED1 Entity disambiguation (via context triple) batch_69c72f6514948190a5562201e7b36e27 completed March 28, 2026, 1:31 a.m.
Created at: March 22, 2026, 3:58 p.m.