Triple
T1829769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EUMM Georgia |
E40734
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | civilian monitoring mission |
C1218
|
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: civilian monitoring mission Context triple: [EUMM Georgia, instanceOf, civilian monitoring mission]
-
A.
military mission
A military mission is a coordinated operation undertaken by armed forces to achieve specific strategic, operational, or tactical objectives within defined constraints and rules of engagement.
-
B.
international monitoring mechanism
chosen
An international monitoring mechanism is a structured system, often established by states or international organizations, that systematically observes, evaluates, and reports on compliance with agreed-upon international norms, laws, or standards across borders.
-
C.
United Nations peacekeeping mission
A United Nations peacekeeping mission is an international operation authorized by the UN to help maintain or restore peace and security in conflict-affected areas through the deployment of military, police, and civilian personnel under impartial mandates.
-
D.
multinational mission mechanism
A multinational mission mechanism is a structured framework of processes, agreements, and coordinating bodies that enables multiple countries or organizations to collaboratively plan, resource, and execute a shared mission across borders.
-
E.
military operation
A military operation is a coordinated and planned set of actions conducted by armed forces to achieve specific strategic, operational, or tactical objectives.
- F. None of above.
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_69a8864644bc8190b2358ab897194ac1 |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:32 p.m.