Triple
T31140485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Athena mechanism |
E793768
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | intergovernmental administrative arrangement |
C21134
|
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: intergovernmental administrative arrangement Context triple: [Athena mechanism, instanceOf, intergovernmental administrative arrangement]
-
A.
intergovernmental organization
An intergovernmental organization is a formal entity created by sovereign states through treaties or agreements to cooperate on common interests, coordinate policies, and address international issues.
-
B.
interagency coordination arrangement
An interagency coordination arrangement is a structured agreement or framework that defines how multiple government or organizational agencies collaborate, share information, and align responsibilities to achieve common objectives.
-
C.
intergovernmental board
An intergovernmental board is a formal decision-making body composed of representatives from multiple governments that coordinates policies, oversees joint initiatives, and manages shared responsibilities across participating states.
-
D.
intergovernmental partnership
chosen
An intergovernmental partnership is a collaborative arrangement in which two or more governments coordinate policies, resources, and actions to address shared issues or achieve common goals.
-
E.
intergovernmental coordination agency
An intergovernmental coordination agency is an organization formed by multiple governments to align policies, share information, and manage joint initiatives across jurisdictions.
- 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:05 p.m.