Triple

T2990204
Position Surface form Disambiguated ID Type / Status
Subject Aalsmeer E80730 entity
Predicate borderedBy P224 FINISHED
Object Uithoorn E62757 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: Uithoorn | Statement: [Aalsmeer, borderedBy, Uithoorn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Uithoorn
Context triple: [Aalsmeer, borderedBy, Uithoorn]
  • A. Uithoorn chosen
    Uithoorn is a town and municipality in the province of North Holland in the Netherlands, situated along the Amstel River.
  • B. Nieuwenhoorn
    Nieuwenhoorn is a village in the western Netherlands that forms part of the province of South Holland.
  • C. Oosterwijtwerd
    Oosterwijtwerd is a small village in the province of Groningen in the northern Netherlands, known for its rural character and historic church.
  • D. Oosterhout
    Oosterhout is a town and municipality in the southern Netherlands known for its historic monasteries and proximity to the city of Breda.
  • E. Deurne
    Deurne is a district of the Belgian city of Antwerp, known for its residential neighborhoods and green spaces such as Rivierenhof park.
  • 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_69ad8b16c3488190b47b6aa7a59a335b completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad99de55208190bc56ecbe08638e5a completed March 8, 2026, 3:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69bfe8ba08f88190a0b10b7a0a05b98c completed March 22, 2026, 1:03 p.m.
Created at: March 8, 2026, 2:59 p.m.