Triple

T17583395
Position Surface form Disambiguated ID Type / Status
Subject René II, Duke of Lorraine E428257 entity
Predicate associatedWithPlace P2830 FINISHED
Object Barrois NE NERFINISHED

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: Barrois | Statement: [René II, Duke of Lorraine, associatedWithPlace, Barrois]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Barrois
Context triple: [René II, Duke of Lorraine, associatedWithPlace, Barrois]
  • A. Barrois chosen
    Barrois is a historical region in northeastern France that formed the core territory of the medieval County of Bar.
  • B. Creillois
    Creillois is the French term for inhabitants of the town of Creil in northern France.
  • C. Rouvroy
    Rouvroy is a small municipality in the Walloon region of southern Belgium, located within Luxembourg Province near the French border.
  • D. Hesbaye
    Hesbaye is a historical region in present-day Belgium, known for its fertile agricultural land and early medieval significance within the Frankish realms.
  • E. Langrois
    Langrois is the French term for an inhabitant or native of the town of Langres in northeastern France.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d889e1030481909950e140c63255b9 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e463cf556881908d2935b3761f65df completed April 19, 2026, 5:10 a.m.
Created at: April 10, 2026, 5:50 a.m.