Triple

T20075338
Position Surface form Disambiguated ID Type / Status
Subject Heinenoord Tunnel E499846 entity
Predicate namedAfter P63 FINISHED
Object Heinenoord 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: Heinenoord | Statement: [Heinenoord Tunnel, namedAfter, Heinenoord]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Heinenoord
Context triple: [Heinenoord Tunnel, namedAfter, Heinenoord]
  • A. Heinenoord chosen
    Heinenoord is a village in the Dutch province of South Holland, known for its rural character and the nearby Heinenoord Tunnel under the Oude Maas river.
  • B. Noorderhaaks
    Noorderhaaks is a small, uninhabited sandbar island off the Dutch coast, forming the westernmost part of the West Frisian Islands archipelago.
  • C. Noordoewer
    Noordoewer is a small border town in southern Namibia on the Orange River, serving as a key road crossing point into South Africa.
  • D. Langeveen
    Langeveen is a small village in the Dutch province of Overijssel, located within the municipality of Tubbergen.
  • E. Monnickendam
    Monnickendam is a historic fishing town in North Holland, Netherlands, known for its well-preserved old harbor and traditional Dutch architecture.
  • 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_69da627770948190997f486f9a2e370f completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e6643ab0448190ab18d013b72aaf32 completed April 20, 2026, 5:36 p.m.
Created at: April 11, 2026, 3:40 p.m.