Triple

T35154830
Position Surface form Disambiguated ID Type / Status
Subject Gunwingguan languages E1015088 entity
Predicate primaryConsonantPlace P75741 FINISHED
Object multipleCoronalSeries 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: multipleCoronalSeries | Statement: [Gunwingguan languages, primaryConsonantPlace, multipleCoronalSeries]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: primaryConsonantPlace
Context triple: [Gunwingguan languages, primaryConsonantPlace, multipleCoronalSeries]
  • A. hasConsonantPlace
    Indicates that a consonant sound is articulated at a particular place of articulation in the vocal tract.
  • B. placeOfArticulation chosen
    Indicates the specific location within the vocal tract where a speech sound is produced.
  • C. hasConsonantManner
    Indicates that one sound is related to another by sharing a specific manner of consonant articulation (e.g., stop, fricative, nasal).
  • D. hasNasalConsonants
    Indicates that the subject language or word includes one or more nasal consonant sounds in its phonological inventory or pronunciation.
  • E. primaryPhonologicalSystem
    Indicates that one phonological system is the main or dominant sound system associated with a given language, dialect, or linguistic entity.
  • 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_69f76ddb3a708190b521ba2970b17178 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_6a037c8c34f88190ace26f555827f23e completed May 12, 2026, 7:16 p.m.
PD Predicate disambiguation batch_6a037a016960819093ed4990fb4d9d36 completed May 12, 2026, 7:05 p.m.
Created at: May 3, 2026, 4:02 p.m.