Triple
T21567613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Шанхайская пятёрка |
E532201
|
entity |
| Predicate | языкРаботы |
P118239
|
FINISHED |
| Object | русский язык |
—
|
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: русский язык | Statement: [Шанхайская пятёрка, языкРаботы, русский язык]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: языкРаботы Context triple: [Шанхайская пятёрка, языкРаботы, русский язык]
-
A.
primaryLanguageInWork
chosen
Indicates that a specified language is the main or predominant language used within a particular work (such as a book, film, or document).
-
B.
workLanguageVariant
Indicates that one language variant of a work is related to another version of the same work, typically differing by language or localization.
-
C.
languageOfUnderlyingWork
Indicates the language in which the original or underlying work (from which a derived or related work stems) is expressed.
-
D.
workLanguageOfTitle
Indicates the language in which a specific work or title is expressed or written.
-
E.
languageWithinWork
Indicates that a specific language is used or contained within a particular work (such as a document, publication, or creative piece).
- 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_69e0c460db088190828c64206a450273 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eee9c9f264819085b4807923860793 |
completed | April 27, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:30 p.m.