Triple

T37047503
Position Surface form Disambiguated ID Type / Status
Subject Kusaasi E916956 entity
Predicate ethnologueLanguageCode P36930 FINISHED
Object kus LITERAL 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: kus | Statement: [Kusaasi, ethnologueLanguageCode, kus]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ethnologueLanguageCode
Context triple: [Kusaasi, ethnologueLanguageCode, kus]
  • A. ISO639-3CodeOfLanguage chosen
    Indicates that one entity is the ISO 639-3 three-letter language code assigned to the language represented by the other entity.
  • B. ISO639-3Type
    Indicates the classification type assigned to a language within the ISO 639-3 standard (e.g., living, extinct, ancient, constructed, or special).
  • C. glottocode
    Indicates the standardized Glottolog code that uniquely identifies the language or dialect associated with an entity.
  • D. sharesISO639-3CodeWith
    Indicates that two language entities share the same ISO 639-3 code, meaning they are treated as the same language in that coding system.
  • E. ISO639CollectiveCode
    Indicates that the relationship assigns or associates an ISO 639 collective language code (a code representing a group of related languages) to the relevant language entity or set of languages.
  • F. None of above.

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_69f76e94d0308190a3f06890e133c88e completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fb6fdc7eb081908ab8475efb38c430 completed May 6, 2026, 4:44 p.m.
PD Predicate disambiguation batch_69fb5a986e588190b7a10892bd2ff44c completed May 6, 2026, 3:13 p.m.
Created at: May 3, 2026, 4:14 p.m.