Triple
T1137383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tatar language |
E23170
|
entity |
| Predicate | primaryScriptInRussia |
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: [Tatar language, primaryScriptInRussia, Cyrillic script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryScriptInRussia Context triple: [Tatar language, primaryScriptInRussia, Cyrillic script]
-
A.
primaryScript
Indicates the writing system or script that is chiefly used to represent the language or content of an entity.
-
B.
associatedLanguageScript
chosen
Indicates that there is a relationship between a language and the script or writing system used to represent it.
-
C.
officialScriptOf
Indicates that one writing system is formally designated as the standard or legally recognized script used for a particular language, region, or entity.
-
D.
primaryMedium
Indicates the main material, format, or channel through which something is created, expressed, or communicated.
-
E.
formerScript
Indicates that an entity previously served as the script or writing system for another entity, but is no longer used in that role.
- 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_69a493ec75988190b63a11bafaec29b4 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bde18d208190848c189b2b8d585f |
completed | March 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4b52d48190bec2e7ad1cc8efc0 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.