Triple

T5030447
Position Surface form Disambiguated ID Type / Status
Subject historic town center of Cuijk E113286 entity
Predicate locatedIn P40 FINISHED
Object Cuijk E444188 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: Cuijk | Statement: [historic town center of Cuijk, locatedIn, Cuijk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cuijk
Context triple: [historic town center of Cuijk, locatedIn, Cuijk]
  • A. Cuijk chosen
    Cuijk is a historic town in the Dutch province of North Brabant, known for its Roman-era heritage and location along the River Meuse.
  • B. Zoeterwoude
    Zoeterwoude is a small Dutch municipality and village known for its rural character and location near Leiden in the province of South Holland.
  • C. Roosendaal
    Roosendaal is a city in the southern Netherlands known as a regional center for commerce and transport near the Belgian 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. 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.
  • 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_69bd443775e48190a646ffbfc4334723 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd739099a0819099c6201d4e1c5ee2 completed March 20, 2026, 4:19 p.m.
NED1 Entity disambiguation (via context triple) batch_69e4963545f481909ecc360480b1fc37 completed April 19, 2026, 8:45 a.m.
Created at: March 20, 2026, 1:36 p.m.