Triple

T5893391
Position Surface form Disambiguated ID Type / Status
Subject Loon op Zand E131043 entity
Predicate borderedBy P224 FINISHED
Object Heusden E232561 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: Heusden | Statement: [Loon op Zand, borderedBy, Heusden]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Heusden
Context triple: [Loon op Zand, borderedBy, Heusden]
  • A. Heusden chosen
    Heusden is a historic fortified town in the southern Netherlands known for its well-preserved ramparts and picturesque old harbor.
  • 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. Leusden
    Leusden is a Dutch town and municipality in the central Netherlands, known for its green residential character and proximity to the city of Amersfoort.
  • D. Nieuwendijk
    Nieuwendijk is one of Amsterdam’s oldest and busiest shopping streets, running through the historic city center near Dam Square.
  • E. Goudswaard
    Goudswaard is a small village in the Dutch province of South Holland, known for its rural character and location on the island of Hoeksche Waard.
  • 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_69c124f946348190ab6fa7c2c203924f completed March 23, 2026, 11:33 a.m.
Created at: March 22, 2026, 3:58 p.m.