Triple
T32038081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European space and defense agencies |
E818147
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | intergovernmental organizations |
C280
|
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 organizations Context triple: [European space and defense agencies, instanceOf, intergovernmental organizations]
-
A.
intergovernmental organization
chosen
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.
international organization
An international organization is an institutional entity formed by multiple countries or global actors to coordinate policies, manage shared interests, and address transnational issues through cooperative frameworks and agreements.
-
C.
transnational organization
A transnational organization is an entity that operates across multiple countries, coordinating activities, resources, and decision-making beyond the authority or boundaries of any single nation-state.
-
D.
intergovernmental organization membership
Intergovernmental organization membership is the formal status by which a state or other eligible entity participates as a member in an intergovernmental organization, with associated rights, obligations, and privileges.
-
E.
international economic organization
An international economic organization is an institution formed by multiple countries to coordinate and regulate economic policies, trade, finance, and development across national borders.
- 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_69f348fbc8148190b3c0f95d4772b153 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:19 a.m.