Triple

T1263457
Position Surface form Disambiguated ID Type / Status
Subject Battle of Oudenarde E12550 entity
Predicate location P40 FINISHED
Object Oudenaarde 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: Oudenaarde | Statement: [Battle of Oudenarde, location, Oudenaarde]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Oudenaarde
Context triple: [Battle of Oudenarde, location, Oudenaarde]
  • 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. 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.
  • C. Hasselt
    Hasselt is a historic small city in the Dutch province of Overijssel, known for its medieval center and canals.
  • D. Hasselt
    Hasselt is a city in northeastern Belgium that serves as the capital of the province of Limburg in the Flemish region.
  • E. Dendermonde
    Dendermonde is a historic city in East Flanders, Belgium, known for its medieval architecture and UNESCO-recognized Ros Beiaard procession.
  • 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_69a4933352e08190ac617291985e76c0 completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a4bfc8d6908190a5b2cf1051cc6d5e completed March 1, 2026, 10:38 p.m.
NED1 Entity disambiguation (via context triple) batch_69ae1fa73fe8819097bcd6c07793bc52 completed March 9, 2026, 1:17 a.m.
Created at: March 1, 2026, 7:50 p.m.