Triple

T3844421
Position Surface form Disambiguated ID Type / Status
Subject Bishopric of Bruges E93533 entity
Predicate locatedIn P40 FINISHED
Object Bruges 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: Bruges | Statement: [Bishopric of Bruges, locatedIn, Bruges]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bruges
Context triple: [Bishopric of Bruges, locatedIn, Bruges]
  • A. Bruges chosen
    Bruges is a historic Belgian city renowned for its well-preserved medieval architecture, picturesque canals, and rich artistic heritage.
  • B. 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.
  • C. Maastricht
    Maastricht is a historic city in the southeastern Netherlands known for its medieval architecture, vibrant cultural scene, and as the birthplace of the Maastricht Treaty that founded the European Union.
  • D. 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.
  • 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_69aed96ce578819084ab16e3439976c9 completed March 9, 2026, 2:30 p.m.
NER Named-entity recognition batch_69aeebb655c081909ec5ff3d09eb4778 completed March 9, 2026, 3:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5337284608190af9c288033d5ce23 completed March 14, 2026, 10:07 a.m.
Created at: March 9, 2026, 3:18 p.m.