Triple

T6753729
Position Surface form Disambiguated ID Type / Status
Subject Asten E154400 entity
Predicate borderedBy P224 FINISHED
Object Heeze-Leende E513523 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: Heeze-Leende | Statement: [Asten, borderedBy, Heeze-Leende]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Heeze-Leende
Context triple: [Asten, borderedBy, Heeze-Leende]
  • A. Heeze-Leende chosen
    Heeze-Leende is a municipality in the southern Netherlands known for its rural character, forests, and historic estates.
  • B. Deurne
    Deurne is a district of the Belgian city of Antwerp, known for its residential neighborhoods and green spaces such as Rivierenhof park.
  • C. Eeklo
    Eeklo is a small city and municipality in northwestern Belgium known for its historic town center and location in the Flemish region.
  • D. Nieuwendijk
    Nieuwendijk is one of Amsterdam’s oldest and busiest shopping streets, running through the historic city center near Dam Square.
  • E. Hansweert
    Hansweert is a small village in the Dutch province of Zeeland, known historically as a canal and shipping hub along the Western Scheldt.
  • 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_69c6880fd5808190be684854081e27dd completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d1f32fa08190bb23dc24fef14c8d completed March 27, 2026, 6:52 p.m.
NED1 Entity disambiguation (via context triple) batch_69cfd04f80fc8190aae7c4823ddecb4a completed April 3, 2026, 2:35 p.m.
Created at: March 27, 2026, 2:11 p.m.