Triple
T21733275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kazakh Cyrillic alphabet |
E536459
|
entity |
| Predicate | hasAdditionalLettersForKazakh |
P9187
|
FINISHED |
| Object | Ә |
—
|
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: Ә | Statement: [Kazakh Cyrillic alphabet, hasAdditionalLettersForKazakh, Ә]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdditionalLettersForKazakh Context triple: [Kazakh Cyrillic alphabet, hasAdditionalLettersForKazakh, Ә]
-
A.
hasAdditionalLetters
chosen
Indicates that one entity contains extra or more letters than another entity, beyond a specified base set or reference.
-
B.
usesAdditionalLettersFrom
Indicates that one entity forms or derives its representation by incorporating extra letters taken from another entity beyond those originally present.
-
C.
hasCyrillicAlphabetForm
Indicates that an entity has a corresponding representation or form written in the Cyrillic alphabet.
-
D.
hasBasicLetters
Indicates that an entity contains or is composed of fundamental alphabetic characters, without additional symbols or diacritics.
-
E.
hasLettersFor
Indicates that one entity possesses or contains written correspondence intended for 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_69e0c46d3284819099a4f9d5a704eb95 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69effd085eec81908b3df82bc25a8780 |
completed | April 28, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e6969c16fc8190b5126c169317d85d |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:48 p.m.