Triple

T11784430
Position Surface form Disambiguated ID Type / Status
Subject Belley E280234 entity
Predicate demonym P191 FINISHED
Object Belleyssien E280234 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: Belleyssien | Statement: [Belley, demonym, Belleyssien]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Belleyssien
Context triple: [Belley, demonym, Belleyssien]
  • A. Belley chosen
    Belley is a historic town in eastern France that serves as one of the administrative centers of the Ain department in the Auvergne-Rhône-Alpes region.
  • B. Bellabeg
    Bellabeg is a small village in Strathdon, Aberdeenshire, Scotland, known for its role as the starting point of the annual Lonach Highland Gathering and March.
  • C. Bihorel
    Bihorel is a suburban commune in northern France, located near Rouen and integrated into its public transport network.
  • D. Belasyse
    Belasyse is an English noble family name historically associated with aristocratic titles such as the Earls Fauconberg.
  • E. Bessas
    Bessas was a prominent 6th-century Byzantine general under Emperor Justinian I, noted for his role in the Gothic and Lazic Wars.
  • 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_69d6ab258b808190b1735835c841e3a4 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d8a585795c8190aa8a5edf0d99b47f completed April 10, 2026, 7:23 a.m.
NED1 Entity disambiguation (via context triple) batch_69f090d861f481909b920197a3d60e28 completed April 28, 2026, 10:50 a.m.
Created at: April 8, 2026, 9:42 p.m.