Triple
T1926898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgian language |
E40852
|
entity |
| Predicate | hasPhonemicConsonants |
P24463
|
FINISHED |
| Object | over 30 consonants |
—
|
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: over 30 consonants | Statement: [Georgian language, hasPhonemicConsonants, over 30 consonants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhonemicConsonants Context triple: [Georgian language, hasPhonemicConsonants, over 30 consonants]
-
A.
hasConsonantPhonemes
chosen
Indicates that an entity possesses or includes one or more consonant phonemes in its phonological system.
-
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.
hasPhonemicContrast
Indicates that two or more speech sounds are distinguished in a language by differences that change word meaning.
-
D.
hasConsonantSigns
Indicates that one entity possesses or includes consonant sign characters as part of its representation or structure.
-
E.
hasPhonemeInventory
Indicates that an entity possesses a specific set or system of distinct speech sounds (phonemes) used in its language.
- 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_69a8864711648190b07bed24ed76258e |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb261ef8481909be2390ac5a02622 |
completed | March 7, 2026, 5:06 a.m. |
| PD | Predicate disambiguation | batch_69abafeec6f881909d47acb966683279 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.