Triple
T3750902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Audenarde |
E81325
|
entity |
| Predicate | hasDutchName |
P744
|
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: [Audenarde, hasDutchName, Oudenaarde]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oudenaarde Context triple: [Audenarde, hasDutchName, 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.
Roeselare
Roeselare is a city in western Belgium known as an economic and commercial center in the province of West Flanders.
-
D.
Eupen
Eupen is a town in eastern Belgium that serves as the administrative center of the country’s German-speaking Community.
-
E.
Hasselt
Hasselt is a historic small city in the Dutch province of Overijssel, known for its medieval center and canals.
- 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_69ad8b19b7b08190a6188804e99c53e9 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb909bb4819088559f90d718f72f |
completed | March 8, 2026, 7:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be89b0441881908b87c7a62434e79a |
completed | March 21, 2026, 12:06 p.m. |
Created at: March 8, 2026, 3:35 p.m.