Triple

T10775771
Position Surface form Disambiguated ID Type / Status
Subject western Sudan E254192 entity
Predicate hasLanguage P15 FINISHED
Object Fur language E49227 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: Fur language | Statement: [western Sudan, hasLanguage, Fur language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fur language
Context triple: [western Sudan, hasLanguage, Fur language]
  • A. Fur language chosen
    The Fur language is an Eastern Sudanic language spoken primarily by the Fur people of western Sudan, especially in the Darfur region.
  • B. Fur
    Fur is a Nilo-Saharan language spoken primarily by the Fur people of western Sudan’s Darfur region.
  • C. Fur
    Fur is a small Danish island in the Limfjord, renowned for its dramatic cliffs, fossil-rich moler clay deposits, and scenic coastal landscapes.
  • D. Fox language
    Fox language is a Native American Algonquian language traditionally spoken by the Meskwaki (Fox), Sauk, and Kickapoo peoples of the central United States.
  • E. Sac and Fox language
    The Sac and Fox language is an Algonquian Native American language traditionally spoken by the Sauk and Meskwaki (Fox) peoples of the central United States.
  • 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_69d6aa609f008190a294200aefcb7bd5 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d7329cc6c881908f827edff941d456 completed April 9, 2026, 5:01 a.m.
NED1 Entity disambiguation (via context triple) batch_69de238ff88881908676d38dca041cb4 completed April 14, 2026, 11:22 a.m.
Created at: April 8, 2026, 9:16 p.m.