Triple

T10796684
Position Surface form Disambiguated ID Type / Status
Subject Nyuong Nuer E254724 entity
Predicate hasPhonologicalFeaturesInCommonWith P8038 FINISHED
Object other Nuer dialects 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: other Nuer dialects | Statement: [Nyuong Nuer, hasPhonologicalFeaturesInCommonWith, other Nuer dialects]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPhonologicalFeaturesInCommonWith
Context triple: [Nyuong Nuer, hasPhonologicalFeaturesInCommonWith, other Nuer dialects]
  • A. hasPhonologicalSimilarityTo chosen
    Indicates that two linguistic elements share similar sound patterns or phonological features.
  • B. hasPhonologicalBasisFor
    Indicates that one entity serves as the phonological source, motivation, or foundation for another entity.
  • C. hasPhonologicalParameters
    Indicates that an entity is associated with specific phonological features or parameters that characterize its sound structure.
  • D. hasPhonologicalDescription
    Indicates that an entity is associated with a specific representation or description of its sound structure or phonological form.
  • E. hasPhonemicContrast
    Indicates that two or more speech sounds are distinguished in a language by differences that change word meaning.
  • 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_69d6aa61c15c8190a1839550c56e75e1 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d73332dbfc8190904434846957b618 completed April 9, 2026, 5:03 a.m.
PD Predicate disambiguation batch_69d6f3188f00819094ee8d65b187a333 completed April 9, 2026, 12:30 a.m.
Created at: April 8, 2026, 9:17 p.m.