Triple

T12350987
Position Surface form Disambiguated ID Type / Status
Subject Fortuna Sittard E294483 entity
Predicate homeCity P263 FINISHED
Object Sittard 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: Sittard | Statement: [Fortuna Sittard, homeCity, Sittard]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sittard
Context triple: [Fortuna Sittard, homeCity, Sittard]
  • A. Sittard chosen
    Sittard is a historic city in the Dutch province of Limburg, known for its medieval center and proximity to the German and Belgian borders.
  • B. Harderwijk
    Harderwijk is a historic Dutch city known for its former Hanseatic trading role and scenic location on the shores of the Veluwemeer.
  • C. Schagen
    Schagen is a historic market town and municipality in the province of North Holland in the Netherlands, known for its traditional West Frisian culture and regional role as a local center.
  • D. Wijchen
    Wijchen is a town and municipality in the Dutch province of Gelderland, located just southwest of the city of Nijmegen.
  • 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_69d6ab6ccbec8190b09e2d357aa80064 completed April 8, 2026, 7:24 p.m.
NER Named-entity recognition batch_69d93f7cbff08190849cd2aec4ce3243 completed April 10, 2026, 6:20 p.m.
Created at: April 8, 2026, 9:53 p.m.