Triple
T33487149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OSCE Minsk Group |
E857642
|
entity |
| Predicate | hasCoChairCountry |
P26171
|
FINISHED |
| Object | Russian Federation |
E10011
|
NE 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 Federation | Statement: [OSCE Minsk Group, hasCoChairCountry, Russian Federation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoChairCountry Context triple: [OSCE Minsk Group, hasCoChairCountry, Russian Federation]
-
A.
hasCoChair
Indicates that an entity shares the role of chair (leadership or oversight position) jointly with another entity.
-
B.
hasCoChairFrom
chosen
Indicates that an entity has a co-chair whose affiliation or origin is from a specified source, organization, or group.
-
C.
hasSecretariatCountry
Indicates that an entity has its secretariat located in or administered by a specified country.
-
D.
hasCoChairSystem
Indicates that an entity is associated with or governed by a system in which responsibilities or roles are jointly shared by co-chairs.
-
E.
hasContributingCountry
Indicates that a country has contributed resources, support, or participation to the subject entity or activity.
- F. None of above.
Provenance (4 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_69f3497547608190a1a0f2365fb713ee |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a35afc327e08190b62fc4059b49c254 |
completed | June 19, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:38 a.m.