Triple
T36991303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AmaBhaca |
E915105
|
entity |
| Predicate | usesClickConsonants |
P30577
|
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: [AmaBhaca, usesClickConsonants, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesClickConsonants Context triple: [AmaBhaca, usesClickConsonants, yes]
-
A.
hasClickConsonants
chosen
Indicates that the subject language includes click consonant sounds in its phonemic inventory.
-
B.
usesConsonantInitials
Indicates that an entity’s initials or abbreviated form begin with consonant letters rather than vowels.
-
C.
usesFinalConsonants
Indicates that an entity employs or contains consonant sounds in final position, such as at the end of a word, syllable, or phonological unit.
-
D.
supportsConjunctConsonants
Indicates that a writing system or orthographic convention allows the formation and use of conjunct consonant clusters (combined consonant characters).
-
E.
isConsonant
Indicates that a given character or sound is a consonant rather than a vowel or other symbol.
- 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_69f76e8dd0408190b8b46da118ea5128 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe5c1a502081909d4024e514309c8e |
completed | May 8, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69fe5a9df21c819087153f5d0bcaa987 |
completed | May 8, 2026, 9:50 p.m. |
Created at: May 3, 2026, 4:14 p.m.