Triple
T35952650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unicode Cyrillic block |
E1039771
|
entity |
| Predicate | coversLanguages |
P2177
|
FINISHED |
| Object | Russian |
—
|
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: Russian | Statement: [Unicode Cyrillic block, coversLanguages, Russian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversLanguages Context triple: [Unicode Cyrillic block, coversLanguages, Russian]
-
A.
hasLanguages
Indicates that an entity is associated with one or more languages it uses, supports, or is expressed in.
-
B.
includesLanguage
chosen
Indicates that one entity contains, supports, or makes use of a specified language as part of its content, functionality, or representation.
-
C.
languageOfCoverage
Indicates the language in which the coverage, such as reporting or documentation about something, is expressed.
-
D.
usesWorkingLanguagesOf
Indicates that one entity employs or operates using the working languages associated with another entity.
-
E.
targetsLanguage
Indicates that an action, resource, or entity is specifically directed toward, designed for, or intended to be used with a particular language.
- 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_69f76e25ea488190b7cee970b3e70382 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
Created at: May 3, 2026, 4:07 p.m.