Triple

T18449590
Position Surface form Disambiguated ID Type / Status
Subject Beurnevésin E450743 entity
Predicate officialName P66 FINISHED
Object Beurnevésin 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: Beurnevésin | Statement: [Beurnevésin, officialName, Beurnevésin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Beurnevésin
Context triple: [Beurnevésin, officialName, Beurnevésin]
  • A. Beurnevésin chosen
    Beurnevésin is a small municipality in the canton of Jura in northwestern Switzerland, near the French border.
  • B. Esblygeois
    Esblygeois are the inhabitants or natives of the commune of Esbly in the Île-de-France region of France.
  • C. Creillois
    Creillois is the French term for inhabitants of the town of Creil in northern France.
  • D. Brionnais
    Brionnais is a historic rural region in eastern France known for its Romanesque churches, traditional stone villages, and Charolais cattle farming.
  • E. Plesséiens
    Les Plesséiens sont les habitants de la commune française du Plessis-Pâté, située dans le département de l’Essonne en Île-de-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_69d8d38345688190b565eac2e4cd7935 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e5264748dc8190984501af3e4b2036 completed April 19, 2026, 7 p.m.
Created at: April 10, 2026, 11:30 a.m.