Triple

T1932001
Position Surface form Disambiguated ID Type / Status
Subject Hans van Heeswijk E40965 entity
Predicate workLocation P7 FINISHED
Object Zwolle E353304 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: Zwolle | Statement: [Hans van Heeswijk, workLocation, Zwolle]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Zwolle
Context triple: [Hans van Heeswijk, workLocation, Zwolle]
  • A. Zwolle chosen
    Zwolle is a historic Dutch city in the eastern Netherlands known for its medieval center, cultural heritage, and regional economic importance.
  • B. Venlo
    Venlo is a historic city in the southeastern Netherlands, located near the German border on the river Meuse and known as a regional economic and logistics hub.
  • C. Apeldoorn
    Apeldoorn is a city in the province of Gelderland in the Netherlands, known for the royal palace Het Loo and its historical ties to the Dutch monarchy.
  • D. Hoorn
    Hoorn is a historic port city in the Netherlands known for its role in the Dutch Golden Age and as a former base of the Dutch East India Company.
  • E. Leeuwarden
    Leeuwarden is a historic city in the northern Netherlands, known as the capital of the province of Friesland and for its rich cultural and architectural heritage.
  • 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_69a8864711648190b07bed24ed76258e completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69abb297ec2c819092ad62d72005223d completed March 7, 2026, 5:07 a.m.
NED1 Entity disambiguation (via context triple) batch_69c83414c374819085ca1e441728c6af completed March 28, 2026, 8:03 p.m.
Created at: March 4, 2026, 7:35 p.m.