Triple
T36561511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kabardino-Balkar ASSR |
E901849
|
entity |
| Predicate | usedScriptForKabardian |
P180010
|
FINISHED |
| Object | Cyrillic |
—
|
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: Cyrillic | Statement: [Kabardino-Balkar ASSR, usedScriptForKabardian, Cyrillic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedScriptForKabardian Context triple: [Kabardino-Balkar ASSR, usedScriptForKabardian, Cyrillic]
-
A.
usesScriptFor
Indicates that one entity employs or relies on a particular script or writing system for its representation, communication, or operation.
-
B.
usedInScripts
Indicates that something (such as a tool, method, or resource) is employed or referenced within one or more scripts.
-
C.
usedInSourceLanguageScript
chosen
Indicates that a particular script is employed for writing in a given source language.
-
D.
laterUsedScript
Indicates that one entity adopted or employed the script of another entity at a later point in time.
-
E.
scriptInUrdu
Indicates that the associated content is written or represented using the Urdu script.
- 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:11 p.m.