Triple
T5460232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tajik language |
E122576
|
entity |
| Predicate | standardScriptSince |
P6524
|
FINISHED |
| Object | Cyrillic script since mid-20th century |
—
|
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 since mid-20th century | Statement: [Tajik language, standardScriptSince, Cyrillic script since mid-20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardScriptSince Context triple: [Tajik language, standardScriptSince, Cyrillic script since mid-20th century]
-
A.
standardType
Indicates that one entity is classified as the standard, canonical, or reference type for another entity or context.
-
B.
primaryScript
chosen
Indicates the writing system or script that is chiefly used to represent the language or content of an entity.
-
C.
scriptStandardizationCenter
Indicates a relationship where an entity serves as a center or authority responsible for standardizing a writing system or script.
-
D.
officialScriptOf
Indicates that one writing system is formally designated as the standard or legally recognized script used for a particular language, region, or entity.
-
E.
standardBefore
Indicates that one standard must be satisfied, applied, or occur earlier in sequence or priority than another standard.
- 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_69bd46424248819085282ddf50a565f3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd927c946c8190aef40679199fede3 |
completed | March 20, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69bd91a0d96c8190bd1299edbf764bbb |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:08 p.m.