Triple
T9147018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serbo-Croatian |
E219480
|
entity |
| Predicate | usesCyrillicAlphabetVariant |
P7160
|
FINISHED |
| Object | Serbian Cyrillic alphabet |
—
|
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: Serbian Cyrillic alphabet | Statement: [Serbo-Croatian, usesCyrillicAlphabetVariant, Serbian Cyrillic alphabet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCyrillicAlphabetVariant Context triple: [Serbo-Croatian, usesCyrillicAlphabetVariant, Serbian Cyrillic alphabet]
-
A.
hasCyrillicAlphabetForm
Indicates that an entity has a corresponding representation or form written in the Cyrillic alphabet.
-
B.
usesAlphabet
chosen
Indicates that one entity employs or is written using the alphabet or writing system associated with another entity.
-
C.
usesDiacritics
Indicates that the referenced text or linguistic element employs diacritical marks as part of its written form.
-
D.
usesLatinAlphabetSince
Indicates that an entity has employed the Latin alphabet as its writing system starting from a specific point in time and continuing thereafter.
-
E.
usesSovietSymbols
Indicates that an entity employs or displays symbols associated with the former Soviet Union.
- 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_69ca83e121dc81909912bd66953081c5 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca918a3c881909c34a6a682eb2625 |
completed | April 1, 2026, 5:11 a.m. |
| PD | Predicate disambiguation | batch_69cc6603ce8c8190bf6e8d6754bdec54 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:20 p.m.