Triple
T18635235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peter Mathuki |
E455528
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional integration expert |
C1337
|
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: regional integration expert Context triple: [Peter Mathuki, instanceOf, regional integration expert]
-
A.
trade policy expert
A trade policy expert is a specialist who analyzes, designs, and advises on international trade rules, agreements, and regulations to guide governments or organizations in achieving economic and strategic objectives.
-
B.
international relations scholar
chosen
An international relations scholar is an expert who studies and analyzes the political, economic, and social interactions among states and non-state actors in the global system.
-
C.
regional economic integration protocol
A regional economic integration protocol is a formal agreement among neighboring or closely linked countries that coordinates trade, investment, and regulatory policies to reduce barriers and promote a more unified regional market.
-
D.
regional organisation
A regional organisation is an entity formed by multiple countries or territories within a specific geographic area to coordinate policies, promote cooperation, and address shared economic, political, social, or security issues.
-
E.
theory of European integration
A theory of European integration is a conceptual framework that explains how and why European states transfer authority to, cooperate within, and are transformed by supranational institutions such as the European Union.
- 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_69d8d38cc7948190a55ea64e5638994e |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:46 a.m.