Triple

T16821812
Position Surface form Disambiguated ID Type / Status
Subject Driehuis railway station E408911 entity
Predicate locatedIn P40 FINISHED
Object Driehuis E408911 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: Driehuis | Statement: [Driehuis railway station, locatedIn, Driehuis]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Driehuis
Context triple: [Driehuis railway station, locatedIn, Driehuis]
  • A. Driehuis chosen
    Driehuis is a village in the Dutch province of North Holland, known for its residential character and proximity to the North Sea coast and nearby dunes.
  • B. Trippenhuis
    Trippenhuis is a historic 17th-century canal house in Amsterdam that serves as the headquarters of the Royal Netherlands Academy of Arts and Sciences.
  • C. Houten Huys
    Houten Huys is one of the oldest surviving wooden houses in Amsterdam, located in the historic Begijnhof courtyard.
  • D. Huis ter Heide
    Huis ter Heide is a small village in the Dutch province of Utrecht, known for its wooded surroundings and proximity to the former airbase at Soesterberg.
  • E. De Hoeve
    De Hoeve is a small village in the municipality of Weststellingwerf in the Dutch province of Friesland.
  • 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_69d88394566c8190b3dcbdc72935f7fa completed April 10, 2026, 4:59 a.m.
NER Named-entity recognition batch_69e3b2e77ab88190be1ec8179251864e completed April 18, 2026, 4:35 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00b29a3854819099eed580eea5d84d completed May 10, 2026, 4:30 p.m.
Created at: April 10, 2026, 5:23 a.m.