Triple

T1195306
Position Surface form Disambiguated ID Type / Status
Subject Jan Pieterszoon Coen E25654 entity
Predicate residence P75 FINISHED
Object Hoorn E480395 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: Hoorn | Statement: [Jan Pieterszoon Coen, residence, Hoorn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hoorn
Context triple: [Jan Pieterszoon Coen, residence, Hoorn]
  • A. Hoorn chosen
    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.
  • B. 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.
  • C. Gorinchem
    Gorinchem is a historic fortified city in the Netherlands known for its well-preserved city walls and picturesque old town.
  • D. Helmond
    Helmond is a city in the southern Netherlands known for its historic castle, industrial heritage, and location near Eindhoven in the province of North Brabant.
  • E. Zwolle
    Zwolle is a historic Dutch city in the eastern Netherlands known for its medieval center, cultural heritage, and regional economic importance.
  • 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_69a49429f5ec8190a6a205eb0ae81e5e completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4bd78f61c8190bdba2255d35a8fe4 completed March 1, 2026, 10:28 p.m.
NED1 Entity disambiguation (via context triple) batch_69bfb12cd0e4819082403092672f9fe8 completed March 22, 2026, 9:06 a.m.
Created at: March 1, 2026, 7:46 p.m.