Triple
T21656913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Совет глав правительств ШОС |
E534490
|
entity |
| Predicate | форматЗаседаний |
P3082
|
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.
jointMeetingForms
Indicates that multiple parties come together in a single, coordinated meeting to discuss or decide on shared matters.
-
B.
conferenceFormatUsed
Indicates that a particular conference is conducted using a specified format or modality (e.g., in-person, virtual, hybrid).
-
C.
conferenceFormat
Indicates the type or structure in which a conference is organized or conducted (e.g., in-person, virtual, hybrid, workshop-based).
-
D.
meetingType
chosen
Indicates the specific category or format of a meeting that characterizes how it is organized or conducted.
-
E.
convenesAs
Indicates that an entity brings together or assembles a group, body, or session in a particular role or capacity.
- 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.