Triple

T9721908
Position Surface form Disambiguated ID Type / Status
Subject Battle of the Meuse E235493 entity
Predicate location P40 FINISHED
Object Dinant E587058 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: Dinant | Statement: [Battle of the Meuse, location, Dinant]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dinant
Context triple: [Battle of the Meuse, location, Dinant]
  • A. Dinant chosen
    Dinant is a picturesque Belgian town in Wallonia known for its dramatic cliffs along the Meuse River, its citadel, and as the birthplace of saxophone inventor Adolphe Sax.
  • B. Debourg
    Debourg is a tram terminus and transport hub in Lyon, France, serving as one end of the city’s T1 tram line.
  • C. Couvin
    Couvin is a municipality in southern Belgium known for its extensive forests, caves, and rural landscapes within the Walloon region.
  • D. Comines
    Comines is a town situated along the Lys River in the historic Flanders region on the border between France and Belgium.
  • E. Condroz
    Condroz is a natural region of rolling hills and agricultural landscapes in southern Belgium, spanning parts of several provinces including Liège.
  • 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_69ca84d0123c819096f9dc3b6abb0881 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cd9e42ce948190b52791b27c4456dc completed April 1, 2026, 10:37 p.m.
NED1 Entity disambiguation (via context triple) batch_69d19fa130548190ae729487b90fa8a7 completed April 4, 2026, 11:32 p.m.
Created at: March 30, 2026, 8:20 p.m.