Triple

T9011378
Position Surface form Disambiguated ID Type / Status
Subject Yukpa language E215479 entity
Predicate hasNounClassification P5217 FINISHED
Object animate-inanimate distinction 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: animate-inanimate distinction | Statement: [Yukpa language, hasNounClassification, animate-inanimate distinction]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNounClassification
Context triple: [Yukpa language, hasNounClassification, animate-inanimate distinction]
  • A. hasNounClassSystem chosen
    Indicates that an entity possesses a grammatical system in which nouns are categorized into distinct classes that affect their agreement with other elements in the language.
  • B. hasPronounCategory
    Indicates that an entity is associated with a specific category or type of pronoun (such as personal, possessive, reflexive, etc.).
  • C. hasNounEnding
    Indicates that something possesses or exhibits a particular noun-forming ending or suffix.
  • D. hasNominalMorphology
    Indicates that an entity possesses a system of nominal morphology, such as inflectional or derivational markers on nouns.
  • E. hasNounDeclensionType
    Indicates that a noun is associated with a specific grammatical declension pattern or type.
  • 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_69ca83a2bf088190986ee7a8eb90407d completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc69c1571881908d0b144786b5ee1f completed April 1, 2026, 12:41 a.m.
PD Predicate disambiguation batch_69cc5edf84408190aa5f57cb8bfd00e1 completed March 31, 2026, 11:55 p.m.
Created at: March 30, 2026, 7:06 p.m.