Triple

T23387908
Position Surface form Disambiguated ID Type / Status
Subject Chakma script E593932 entity
Predicate hasPhonographicType P152056 FINISHED
Object segmental writing system 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: segmental writing system | Statement: [Chakma script, hasPhonographicType, segmental writing system]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPhonographicType
Context triple: [Chakma script, hasPhonographicType, segmental writing system]
  • A. hasPhonologicalType
    Indicates that one entity is characterized by or classified as having a particular phonological type (e.g., in terms of sound structure or phonological category).
  • B. phonographicType
    Indicates the specific kind or category of phonographic recording or medium associated with an entity.
  • C. hasPhoneme
    Indicates that a linguistic unit (such as a word or morpheme) contains or includes a particular phoneme as part of its sound structure.
  • D. hasProsodicType
    Indicates that one entity is characterized by a particular prosodic pattern or category (such as stress, intonation, or rhythm type) in relation to another.
  • E. isPhonetic
    Indicates that one entity represents the phonetic (sound-based) form or pronunciation of another entity.
  • F. None of above. chosen

Provenance (4 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_69e25d2754fc819085deea939bde60ab completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1a499bad88190afca1afb2e3fddb0 completed April 29, 2026, 6:26 a.m.
PD Predicate disambiguation batch_69f061dde2e481908308952f9c0d3c2e completed April 28, 2026, 7:29 a.m.
PDg Predicate description generation batch_69f07cbbd7488190ab3c8ae7d0fb68bf completed April 28, 2026, 9:24 a.m.
Created at: April 17, 2026, 5:35 p.m.