Triple
T22652825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mari Autonomous Soviet Socialist Republic |
E559137
|
entity |
| Predicate | usedScriptForMari |
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: [Mari Autonomous Soviet Socialist Republic, usedScriptForMari, Cyrillic script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedScriptForMari Context triple: [Mari Autonomous Soviet Socialist Republic, usedScriptForMari, Cyrillic script]
-
A.
usedInScripts
Indicates that something (such as a tool, method, or resource) is employed or referenced within one or more scripts.
-
B.
laterUsedScript
Indicates that one entity adopted or employed the script of another entity at a later point in time.
-
C.
scriptUsedForLanguage
chosen
Indicates that a particular writing script is employed to write or represent a given language.
-
D.
usesScriptDerivedFrom
Indicates that one entity employs a writing system that is historically or structurally derived from the script used by another entity.
-
E.
scriptUsedCurrently
Indicates that a particular writing system or script is the one presently in use for a given language, text, or context.
- 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_69e245489dd88190b1f674acf61c8769 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1703d7d648190aafe275cd04c47cf |
completed | April 29, 2026, 2:43 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:06 p.m.