Triple

T31950260
Position Surface form Disambiguated ID Type / Status
Subject Keresan E815759 entity
Predicate languageFamilyClassification P86527 FINISHED
Object independent language family 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: independent language family | Statement: [Keresan, languageFamilyClassification, independent language family]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: languageFamilyClassification
Context triple: [Keresan, languageFamilyClassification, independent language family]
  • A. languageFamily
    Indicates that two or more languages belong to the same genealogical language family or linguistic lineage.
  • B. languageFamilyOf
    Indicates that one entity is the language family to which the other entity (a specific language) belongs.
  • C. languageIsolateFamily chosen
    Indicates that a language belongs to a language family that has no demonstrable genetic relationship to any other known language family.
  • D. languageFamilyAssociation
    Indicates an association where one entity belongs to, is classified under, or is related to a particular language family.
  • E. languageFamilyContext
    Indicates the broader linguistic family or grouping within which a particular language or linguistic element is situated.
  • 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_69f348f42d188190a33fc8d20ec50517 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69ffb5c373948190a6606e8caa87a384 completed May 9, 2026, 10:31 p.m.
PD Predicate disambiguation batch_69ffb261da788190b41399df8ed895e8 completed May 9, 2026, 10:17 p.m.
Created at: May 1, 2026, 12:07 a.m.