Triple
T380320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lisbon Strategy |
E8663
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | European Union development strategy |
C2119
|
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: European Union development strategy Context triple: [Lisbon Strategy, instanceOf, European Union development strategy]
-
A.
European intergovernmental organization
A European intergovernmental organization is a cooperative institution formed by European states through treaties to coordinate policies, manage shared interests, and address cross-border issues while preserving national sovereignty.
-
B.
United Nations role
The "United Nations role" conceptual class represents the specific function, responsibility, or position an entity holds within the UN system, such as mediator, peacekeeper, observer, or member state.
-
C.
World Bank position
A World Bank position is a professional role within the World Bank Group responsible for designing, managing, or supporting international development projects, policies, and financial operations aimed at reducing poverty and promoting sustainable economic growth.
-
D.
United States foreign policy doctrine
A United States foreign policy doctrine is a guiding framework of principles and strategic priorities that shapes how the U.S. engages with other nations and responds to international challenges.
-
E.
pan-African organization
A pan-African organization is an entity that promotes political, economic, social, and cultural cooperation and unity among African countries and peoples across the continent and diaspora.
- F. None of above. chosen
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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.