Triple

T15150769
Position Surface form Disambiguated ID Type / Status
Subject Siege of Antwerp E361934 entity
Predicate location P40 FINISHED
Object Antwerp E32042 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: Antwerp | Statement: [Siege of Antwerp, location, Antwerp]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Antwerp
Context triple: [Siege of Antwerp, location, Antwerp]
  • A. Antwerp chosen
    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.
  • B. Ghent
    Ghent is a small unincorporated community and ski-area destination located in Raleigh County, West Virginia, United States.
  • C. 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.
  • D. Tervuren
    Tervuren is a municipality in Flemish Brabant, Belgium, known for its historic park, royal connections, and the Royal Museum for Central Africa.
  • E. 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.
  • 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_69d85a0759908190b8a051d2e2a1cbe6 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e005c934048190afac78a8023a544a completed April 15, 2026, 9:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69fed318aa908190a59b0def01a9cb16 completed May 9, 2026, 6:24 a.m.
Created at: April 10, 2026, 3:07 a.m.