Triple
T22954745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chuvash ASSR |
E570722
|
entity |
| Predicate | usedScriptForChuvashLanguage |
P56657
|
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 ASSR, usedScriptForChuvashLanguage, Cyrillic script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedScriptForChuvashLanguage Context triple: [Chuvash ASSR, usedScriptForChuvashLanguage, Cyrillic script]
-
A.
scriptUsedForLanguage
chosen
Indicates that a particular writing script is employed to write or represent a given language.
-
B.
languageOfScriptPromoted
Indicates that a particular language is associated with and promoted through the use of a given writing script.
-
C.
associatedLanguageScript
Indicates that there is a relationship between a language and the script or writing system used to represent it.
-
D.
usesScriptingLanguage
Indicates that an entity employs a scripting language to perform its operations, configuration, or automation tasks.
-
E.
laterUsedScript
Indicates that one entity adopted or employed the script of another entity at a later point in time.
- 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_69e245b212a88190b5259caf51606084 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181ef7db4819093ab8117ed53c174 |
completed | April 29, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:46 p.m.