Triple

T13254186
Position Surface form Disambiguated ID Type / Status
Subject Gorssel E315614 entity
Predicate locatedNear P294 FINISHED
Object Zutphen 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: Zutphen | Statement: [Gorssel, locatedNear, Zutphen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Zutphen
Context triple: [Gorssel, locatedNear, Zutphen]
  • A. Zutphen chosen
    Zutphen is a historic city in the eastern Netherlands known for its well-preserved medieval center and location along the river IJssel.
  • B. Culemborg
    Culemborg is a historic town in the Dutch province of Gelderland, known for its medieval center and role in the early Dutch colonial era.
  • C. Rijkevoort
    Rijkevoort is a village in the Dutch province of North Brabant, known for its rural character and location near the German border.
  • D. Woerden
    Woerden is a historic Dutch city and municipality in the central Netherlands, known for its medieval fortifications and traditional cheese market.
  • E. Schoonhoven
    Schoonhoven is a historic Dutch town in South Holland, renowned for its silver craftsmanship and picturesque riverside setting.
  • 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_69d806b1072881909e46bd212259c5f0 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d98f7517048190b4eac4e44e81ff66 completed April 11, 2026, 12:01 a.m.
Created at: April 9, 2026, 9:24 p.m.