Triple

T8952720
Position Surface form Disambiguated ID Type / Status
Subject Prince Charles, Count of Flanders E213393 entity
Predicate placeOfDeath P21 FINISHED
Object Ostend E128320 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: Ostend | Statement: [Prince Charles, Count of Flanders, placeOfDeath, Ostend]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ostend
Context triple: [Prince Charles, Count of Flanders, placeOfDeath, Ostend]
  • A. Ostend chosen
    Ostend is a Belgian coastal city on the North Sea known for its beaches, port, and seaside tourism.
  • B. Ostend
    Ostend is a small residential and commercial settlement on Waiheke Island in New Zealand’s Hauraki Gulf.
  • C. Gravelines
    Gravelines is a coastal commune in northern France known for its historic fortifications and strategic position along the English Channel.
  • D. Bruges
    Bruges is a historic Belgian city renowned for its well-preserved medieval architecture, picturesque canals, and rich artistic heritage.
  • E. 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.
  • 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_69ca8399ad2081909f8fa41d4314c215 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc670f88d0819085d7308a5cf6c764 completed April 1, 2026, 12:30 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfc210302c8190b1c062fcbcfeb0f6 completed April 3, 2026, 1:35 p.m.
Created at: March 30, 2026, 6:59 p.m.