Triple
T29521800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yi script |
E748954
|
entity |
| Predicate | hasPhonographicAspect |
P66751
|
FINISHED |
| Object | syllabic representation |
—
|
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: syllabic representation | Statement: [Yi script, hasPhonographicAspect, syllabic representation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhonographicAspect Context triple: [Yi script, hasPhonographicAspect, syllabic representation]
-
A.
hasPhonographicType
Indicates that an entity is associated with a specific type or category of phonographic recording or medium.
-
B.
hasPhoneme
Indicates that a linguistic unit (such as a word or morpheme) contains or includes a particular phoneme as part of its sound structure.
-
C.
hasPhonologicalDescription
chosen
Indicates that an entity is associated with a specific representation or description of its sound structure or phonological form.
-
D.
hasPhonologicalParameters
Indicates that an entity is associated with specific phonological features or parameters that characterize its sound structure.
-
E.
isPhonetic
Indicates that one entity represents the phonetic (sound-based) form or pronunciation of another 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_69f0bd46d99c81908ba9d01cc1dbef7d |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 28, 2026, 4:42 p.m.