Triple

T1464094
Position Surface form Disambiguated ID Type / Status
Subject Nièvre E31578 entity
Predicate hasDemonym P191 FINISHED
Object Nivernais E150661 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: Nivernais | Statement: [Nièvre, hasDemonym, Nivernais]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nivernais
Context triple: [Nièvre, hasDemonym, Nivernais]
  • A. Nivernais chosen
    Nivernais is a historic province in central France, centered around the town of Nevers and known for its rural landscapes and traditional agriculture.
  • B. Brionnais
    Brionnais is a historic rural region in eastern France known for its Romanesque churches, traditional stone villages, and Charolais cattle farming.
  • C. Aube
    Aube is a department in northeastern France known for its historic towns, Champagne vineyards, and rural landscapes.
  • D. Entrèves
    Entrèves is a small alpine village in Italy’s Aosta Valley, near Courmayeur, known as a key gateway settlement at the Italian end of the Mont Blanc region.
  • E. Touraine
    Touraine is a historic region in central France, famed for its Loire Valley châteaux, wine production, and role as a former royal heartland.
  • 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_69a49917dfc081909acdbdf5d684f1ef completed March 1, 2026, 7:52 p.m.
NER Named-entity recognition batch_69a4c5b89708819084fb9ba4ff293b8b completed March 1, 2026, 11:03 p.m.
NED1 Entity disambiguation (via context triple) batch_69ad1c9daa748190865d97f632ab8a37 completed March 8, 2026, 6:52 a.m.
Created at: March 1, 2026, 8 p.m.