Triple

T4945567
Position Surface form Disambiguated ID Type / Status
Subject Baarn E111040 entity
Predicate locatedNear P294 FINISHED
Object Amersfoort E260285 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: Amersfoort | Statement: [Baarn, locatedNear, Amersfoort]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Amersfoort
Context triple: [Baarn, locatedNear, Amersfoort]
  • A. Amersfoort chosen
    Amersfoort is a historic city in the province of Utrecht in the Netherlands, known for its well-preserved medieval center and strategic location as a rail and road hub.
  • 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. 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.
  • D. Haarlem
    Haarlem is a historic Dutch city in the province of North Holland, known for its medieval architecture, cultural heritage, and role as a regional center near Amsterdam.
  • E. Nijmegen
    Nijmegen is a historic Dutch city near the German border that played a crucial strategic role during World War II, particularly in the Allied advance in 1944.
  • 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_69bd441721cc819085c7e33fe0876818 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd70aa890c81908e685ec5e88cae1f completed March 20, 2026, 4:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69e3734e5e688190bbfa472547ef65e8 completed April 18, 2026, 12:04 p.m.
Created at: March 20, 2026, 1:31 p.m.