Triple
T27232790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cyrl |
E682198
|
entity |
| Predicate | associatedUnicodeScript |
P5233
|
FINISHED |
| Object | Cyrillic |
—
|
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 | Statement: [Cyrl, associatedUnicodeScript, Cyrillic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedUnicodeScript Context triple: [Cyrl, associatedUnicodeScript, Cyrillic]
-
A.
hasUnicodeScript
chosen
Indicates that a character or text element belongs to a specific Unicode script category (such as Latin, Cyrillic, or Han).
-
B.
associatedLanguageScript
Indicates that there is a relationship between a language and the script or writing system used to represent it.
-
C.
nativeNameScript
Indicates the writing system or script in which an entity’s native name is expressed.
-
D.
UnicodeBlock
Indicates that a character belongs to a specific contiguous range of code points defined as a Unicode block.
-
E.
UnicodeBlockName
Indicates the specific Unicode block to which a given character or code point belongs.
- 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_69eefacdad7881908b7bca61c90a1a1e |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69ffc704e1e88190884928a6a5c55a87 |
completed | May 9, 2026, 11:45 p.m. |
| PD | Predicate disambiguation | batch_69ffc6b483d881908ad872e25fa6abc5 |
completed | May 9, 2026, 11:43 p.m. |
Created at: April 27, 2026, 9:46 a.m.