Triple
T16723905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GAP (Güneydoğu Anadolu Projesi) |
E406419
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | entegre kalkınma projesi |
C18913
|
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: entegre kalkınma projesi Context triple: [GAP (Güneydoğu Anadolu Projesi), instanceOf, entegre kalkınma projesi]
-
A.
infrastructure project
An infrastructure project is a large-scale, organized effort to plan, design, and construct foundational physical systems—such as transportation, utilities, and public facilities—that support a community’s or region’s economic and social activities.
-
B.
regional development programme
chosen
A regional development programme is a coordinated set of policies, investments, and initiatives designed to stimulate economic growth, improve infrastructure, and enhance social well-being within a specific geographic area.
-
C.
planned city
A planned city is an urban area whose layout, infrastructure, and land use are deliberately designed and constructed according to a comprehensive plan before significant settlement occurs.
-
D.
African Union project
An African Union project is a coordinated initiative undertaken by the African Union and its member states to advance continental priorities such as peace, integration, development, and governance across Africa.
-
E.
regional planning program
A regional planning program is an organized framework of policies, strategies, and actions designed to guide the coordinated development, land use, infrastructure, and resource management of a specific geographic area over time.
- 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:20 a.m.