Triple

T1504248
Position Surface form Disambiguated ID Type / Status
Subject Treaty of Nijmegen E33862 entity
Predicate restoredTerritory P13943 FINISHED
Object Oudenarde E100113 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: Oudenarde | Statement: [Treaty of Nijmegen, restoredTerritory, Oudenarde]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Oudenarde
Context triple: [Treaty of Nijmegen, restoredTerritory, Oudenarde]
  • A. Oudenarde chosen
    Oudenarde (Oudenaarde) is a historic town in East Flanders, Belgium, known for its medieval architecture, tapestry production, and role in early modern European conflicts.
  • B. Dendermonde
    Dendermonde is a historic city in East Flanders, Belgium, known for its medieval architecture and UNESCO-recognized Ros Beiaard procession.
  • C. Roeselare
    Roeselare is a city in western Belgium known as an economic and commercial center in the province of West Flanders.
  • D. Woubrugge
    Woubrugge is a village in the Dutch province of South Holland, known for its location along waterways and its traditional rural character.
  • E. Vilvoorde
    Vilvoorde is a city in the Flemish Region of Belgium, located just north of Brussels and known as part of the capital’s broader metropolitan area.
  • 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_69a885f352a4819099b24ff15489dede completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a907d4edd48190a03c85e1a0cc02b1 completed March 5, 2026, 4:34 a.m.
NED1 Entity disambiguation (via context triple) batch_69af173cc94c8190a351334e7645cc0c completed March 9, 2026, 6:53 p.m.
Created at: March 4, 2026, 7:24 p.m.