Triple
T2735670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chuvash Republic |
E60623
|
entity |
| Predicate | usesScriptForChuvashLanguage |
P16462
|
FINISHED |
| Object | Cyrillic script |
—
|
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 script | Statement: [Chuvash Republic, usesScriptForChuvashLanguage, Cyrillic script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesScriptForChuvashLanguage Context triple: [Chuvash Republic, usesScriptForChuvashLanguage, Cyrillic script]
-
A.
associatedLanguageScript
chosen
Indicates that there is a relationship between a language and the script or writing system used to represent it.
-
B.
scriptVariantLanguage
Indicates that a language is a variant distinguished by its writing system or script from another, related language form.
-
C.
usesScriptDerivedFrom
Indicates that one entity employs a writing system that is historically or structurally derived from the script used by another entity.
-
D.
hasUnicodeScript
Indicates that a character or text element belongs to a specific Unicode script category (such as Latin, Cyrillic, or Han).
-
E.
usedScriptureTranslation
Indicates that one entity employed or relied on a particular translation of scripture in its actions, works, or communications.
- 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_69ab4b77febc819095603eb012cd141b |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb1022488190af84e536946b2e37 |
completed | March 7, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69abd82859348190bce3be8f2e9d60ba |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.