Triple
T2897317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Bruges |
E63971
|
entity |
| Predicate | nativeName |
P15
|
FINISHED |
| Object | Brugge |
E41564
|
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: Brugge | Statement: [City of Bruges, nativeName, Brugge]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Brugge Context triple: [City of Bruges, nativeName, Brugge]
-
A.
Ghent
Ghent is a historic city in the Flemish region of Belgium, known for its medieval architecture, canals, and role as a major cultural and economic center in the Middle Ages.
-
B.
Bruges
chosen
Bruges is a historic Belgian city renowned for its well-preserved medieval architecture, picturesque canals, and rich artistic heritage.
-
C.
Antwerp
Antwerp is a major Belgian port city on the River Scheldt, renowned as a global center for the diamond trade and its historic Flemish art and architecture.
-
D.
Leuven
Leuven is a historic Belgian city known for hosting KU Leuven, one of Europe’s leading research universities, and for its vibrant academic and cultural life.
-
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_69ab4c45822c8190830c5f2bb97bcfd0 |
completed | March 6, 2026, 9:51 p.m. |
| NER | Named-entity recognition | batch_69abe08e7b248190a6bb0f6999f99c23 |
completed | March 7, 2026, 8:23 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b595d57bcc8190b2a6e28437a32b93 |
completed | March 14, 2026, 5:07 p.m. |
Created at: March 6, 2026, 10:08 p.m.