Triple

T15876574
Position Surface form Disambiguated ID Type / Status
Subject Gorane people E384965 entity
Predicate selfIdentification P4296 FINISHED
Object Gorane E217445 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: Gorane | Statement: [Gorane people, selfIdentification, Gorane]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gorane
Context triple: [Gorane people, selfIdentification, Gorane]
  • A. Gorane chosen
    Gorane is another name for the Daza people, a Saharan ethnic group primarily inhabiting parts of Chad, Niger, and Libya.
  • B. Gavisse
    Gavisse is a small commune in northeastern France, located in the Moselle department near the border with Luxembourg and Germany.
  • C. Gaume
    Gaume is a culturally distinct region in southern Belgium known for its milder microclimate, French-speaking population, and characteristic rural landscapes.
  • D. Girod
    Girod is a French surname and place name that appears as a variant of the name Giraud.
  • E. Valleiry
    Valleiry is a small French commune in the Haute-Savoie department of the Auvergne-Rhône-Alpes region in southeastern France, near the Swiss border.
  • 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_69d86da4e86481909f1325fdc971b5ec completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e155fdc1b881909d1c82c4c66a195a completed April 16, 2026, 9:34 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffa950a890819092bc1e8895034593 completed May 9, 2026, 9:38 p.m.
Created at: April 10, 2026, 4:51 a.m.