Triple
T21656915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Совет глав правительств ШОС |
E534490
|
entity |
| Predicate | принимаетДокументы |
P111714
|
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.
receivedDocument
Indicates that one entity has been given and taken possession of a document from another entity or source.
-
B.
documentsNow
Indicates that an entity is currently documenting, recording, or writing about another entity at the present time.
-
C.
issuedDocumentOn
Indicates that an entity formally produced or released a document on a specific date or occasion.
-
D.
supportsDocument
Indicates that one entity provides compatibility or functionality for handling, processing, or using a particular document or document type.
-
E.
legalDocumentRatified
chosen
Indicates that a legal document has been formally approved and made officially valid by the appropriate authority or process.
- 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_69e0c467e1f48190af2650b19175abc4 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef5919c9c88190a2ddcf2cefee79a5 |
completed | April 27, 2026, 12:39 p.m. |
| PD | Predicate disambiguation | batch_69e696826c3c81909270791e79760937 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:36 p.m.