Triple
T19677397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shina language |
E472489
|
entity |
| Predicate | hasRetroflexConsonants |
P136517
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Shina language, hasRetroflexConsonants, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRetroflexConsonants Context triple: [Shina language, hasRetroflexConsonants, yes]
-
A.
hasNasalConsonants
Indicates that the subject language or word includes one or more nasal consonant sounds in its phonological inventory or pronunciation.
-
B.
hasNasalVowels
Indicates that the subject language or phonological system includes vowels that are produced with nasal airflow (nasalized vowels).
-
C.
retroflexesNear
Indicates that one entity bends or curves backward in close proximity to another entity.
-
D.
hasLimitedConsonantInventory
Indicates that a language possesses a relatively small set of distinct consonant sounds in its phonological system.
-
E.
hasEjectiveConsonants
Indicates that a language’s consonant inventory includes ejective consonants, produced with a glottalic egressive airstream mechanism.
- 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_69d8e514f2e08190ba70a4449519d218 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e641bceef881909c5b655af709c8c6 |
completed | April 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69e514eb37b8819091502cc954f70eba |
completed | April 19, 2026, 5:46 p.m. |
| PDg | Predicate description generation | batch_69e5174b060c81908937ff9ff7fce611 |
completed | April 19, 2026, 5:56 p.m. |
Created at: April 10, 2026, 1:45 p.m.