Triple
T21567639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Хартия ШОС |
E532202
|
entity |
| Predicate | устанавливает |
P986
|
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.
establishes
chosen
Indicates that one entity initiates, creates, or formally sets up another entity, relationship, or state, often giving it official or recognized status.
-
B.
overseesInstallation
Indicates that one entity is responsible for supervising and managing the process of installing another entity.
-
C.
establishesOrgan
Indicates that an entity creates, founds, or sets up an organization or institutional body.
-
D.
establishesTest
Indicates that an entity creates or sets up a test or testing procedure for another entity.
-
E.
operatesInstallation
Indicates that an agent is responsible for running, managing, or controlling the functioning of a particular installation.
- 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.