Triple

T443981
Position Surface form Disambiguated ID Type / Status
Subject Pacification of Ghent E10176 entity
Predicate place P373 FINISHED
Object Ghent E53969 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: Ghent | Statement: [Pacification of Ghent, place, Ghent]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ghent
Context triple: [Pacification of Ghent, place, Ghent]
  • A. Ghent chosen
    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. 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.
  • 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. Bruges
    Bruges is a historic Belgian city renowned for its well-preserved medieval architecture, picturesque canals, and rich artistic heritage.
  • E. La Hulpe, Belgium
    La Hulpe is a small municipality in Walloon Brabant, Belgium, known for hosting the headquarters of the global financial messaging network SWIFT and for its nearby Solvay Castle and park.
  • 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_69a2e8465ef481909655c681b01e2986 completed Feb. 28, 2026, 1:06 p.m.
NER Named-entity recognition batch_69a2ef459800819083cd9eef3e7b5295 completed Feb. 28, 2026, 1:36 p.m.
NED1 Entity disambiguation (via context triple) batch_69a533bc40ac81908426b70366259a3b completed March 2, 2026, 6:52 a.m.
Created at: Feb. 28, 2026, 1:11 p.m.