Triple
T965826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coldstream Guards |
E20834
|
entity |
| Predicate | battleHonour |
P12198
|
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: [Coldstream Guards, battleHonour, Oudenarde]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oudenarde Context triple: [Coldstream Guards, battleHonour, 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.
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.
-
D.
Hasselt
Hasselt is a historic small city in the Dutch province of Overijssel, known for its medieval center and canals.
-
E.
Namur
Namur is a historic Belgian city and the capital of Wallonia, located at the confluence of the Meuse and Sambre rivers.
- 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_69a493b33d2c81909c52c369d3ca8436 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b431d61481908b53490e99670363 |
completed | March 1, 2026, 9:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69acbad10ae48190af7dcaa8dfff30ec |
completed | March 7, 2026, 11:54 p.m. |
Created at: March 1, 2026, 7:40 p.m.