Triple

T8698194
Position Surface form Disambiguated ID Type / Status
Subject Quechuan E206453 entity
Predicate typicalMorphologicalFeature P6520 FINISHED
Object extensive suffixation 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: extensive suffixation | Statement: [Quechuan, typicalMorphologicalFeature, extensive suffixation]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalMorphologicalFeature
Context triple: [Quechuan, typicalMorphologicalFeature, extensive suffixation]
  • A. linguisticFeature chosen
    Indicates a relationship where a linguistic property, pattern, or characteristic is attributed to or associated with a language-related entity (such as a word, phrase, or text).
  • B. morphologicalClass
    Indicates the classification of an entity based on its morphological form or structural pattern.
  • C. relatedMorphologicalFeature
    Indicates that one entity is connected to another through a shared or corresponding morphological feature or structure.
  • D. notableMorphology
    Indicates that an entity is characterized by a distinctive or noteworthy physical form, structure, or shape.
  • E. hasNominalMorphology
    Indicates that an entity possesses a system of nominal morphology, such as inflectional or derivational markers on nouns.
  • 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_69ca83555b6c8190abe930dd397e863b completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc58af50408190a3b81100a759795e completed March 31, 2026, 11:28 p.m.
PD Predicate disambiguation batch_69cc456bda508190a9aa0fb92760739e completed March 31, 2026, 10:06 p.m.
Created at: March 30, 2026, 6:34 p.m.