Triple
T3020010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations Office to the African Union liaison functions |
E82431
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | liaison function |
C4033
|
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: liaison function Context triple: [United Nations Office to the African Union liaison functions, instanceOf, liaison function]
-
A.
government liaison office
chosen
A government liaison office is an organizational unit that facilitates communication, coordination, and collaboration between a government entity and external stakeholders such as other agencies, businesses, or the public.
-
B.
L-function
An L-function is a complex analytic function, typically expressed as a Dirichlet series with an Euler product, that encodes deep arithmetic information about objects such as numbers, fields, or algebraic varieties.
-
C.
diplomatic mission unit
A diplomatic mission unit is an organizational subdivision within a diplomatic mission responsible for carrying out specific functions such as political, economic, consular, cultural, or administrative activities in support of a state's foreign relations.
-
D.
communication framework
A communication framework is a structured set of principles, protocols, and tools that guide how information is exchanged, interpreted, and managed between parties in a consistent and effective manner.
-
E.
contact language
A contact language is a linguistic system that emerges when speakers of different native languages interact regularly, often combining elements of their languages to facilitate communication.
- 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.