Triple
T11787946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OSCE observers |
E280319
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | OSCE personnel |
C29812
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: OSCE personnel Context triple: [OSCE observers, instanceOf, OSCE personnel]
-
A.
OSCE field mission
An OSCE field mission is a temporary or long-term presence deployed by the Organization for Security and Co-operation in Europe to support participating States in conflict prevention, crisis management, and post-conflict rehabilitation through monitoring, advising, and capacity-building activities.
-
B.
organ of the OSCE
An organ of the OSCE is a principal institutional body within the Organization for Security and Co-operation in Europe that carries out specific mandated functions such as decision-making, conflict prevention, field operations, or administrative support.
-
C.
OSCE decision-making body
The OSCE decision-making body is the principal collective organ within the Organization for Security and Co-operation in Europe responsible for formulating, negotiating, and adopting political, security, and operational decisions by consensus among participating States.
-
D.
United Nations team
A United Nations team is a group of international professionals collaboratively working under UN mandates to address global issues such as peace, security, development, and human rights.
-
E.
Foreign Service personnel
Foreign Service personnel are government employees who represent and advance their nation’s interests abroad through diplomacy, consular services, policy reporting, and public engagement.
- F. None of above. chosen
Provenance (1 batch)
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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:42 p.m.