Triple

T9948294
Position Surface form Disambiguated ID Type / Status
Subject Trique E195261 entity
Predicate hasAlternativeName P39 FINISHED
Object Trique language E225987 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: Trique language | Statement: [Trique, hasAlternativeName, Trique language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Trique language
Context triple: [Trique, hasAlternativeName, Trique language]
  • A. Triqui language chosen
    The Triqui language is an Oto-Manguean indigenous language of southern Mexico, spoken primarily by the Triqui people of Oaxaca.
  • B. Tregami language
    The Tregami language is a lesser-known Indo-Iranian language spoken by the Tregami people in a small mountainous region of eastern Afghanistan.
  • C. Tigre language
    Tigre language is a Semitic language of the Afroasiatic family spoken primarily by the Tigre people in Eritrea and parts of Sudan.
  • D. Picene language
    The Picene language is an extinct Italic language once spoken by the ancient Piceni people in east-central Italy.
  • E. Sa’och language
    The Sa’och language is an endangered Austroasiatic language spoken by the Sa’och people of Cambodia and Thailand, belonging to the Pearic branch.
  • 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_69ca82e96a108190932bd1fc4acd73a0 completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cdb659307c81908279adb641ceef86 completed April 2, 2026, 12:20 a.m.
NED1 Entity disambiguation (via context triple) batch_69d2292b50a881909ff868487639fbfd completed April 5, 2026, 9:19 a.m.
Created at: March 30, 2026, 8:45 p.m.