Triple
T3020011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations Office to the African Union liaison functions |
E82431
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | coordination function |
C11864
|
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: coordination function Context triple: [United Nations Office to the African Union liaison functions, instanceOf, coordination function]
-
A.
coordination wiki
A coordination wiki is a collaboratively maintained online space where individuals and groups document plans, resources, and processes to organize, align, and improve collective action toward shared goals.
-
B.
budget coordination function
A budget coordination function is a mechanism or process that aligns, integrates, and manages financial plans and resource allocations across different units or activities to ensure coherent and efficient use of funds.
-
C.
administrative function
chosen
An administrative function is a conceptual class representing tasks and processes that support the organization, coordination, and control of operations within an institution or system.
-
D.
Euclidean correlation function
A Euclidean correlation function is a Green’s function defined in Euclidean (imaginary-time) spacetime that encodes the correlations between field operators at different points and is related to physical, real-time correlation functions by analytic continuation.
-
E.
coordinate transformation
A coordinate transformation is a mathematical operation that converts the representation of points or vectors from one coordinate system to another while preserving their underlying geometric relationships.
- 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_69ad8b1fb34081908c1b873e2b7273e1 |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3 p.m.