Triple
T15319651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agenzia Interregionale per il fiume Po |
E366254
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | interregional agency |
C1050
|
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: interregional agency Context triple: [Agenzia Interregionale per il fiume Po, instanceOf, interregional agency]
-
A.
interstate agency
An interstate agency is an organization formed by two or more states through a formal agreement to collaboratively manage shared resources, services, or regulatory responsibilities across their borders.
-
B.
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.
-
C.
independent regional agency
chosen
An independent regional agency is an autonomous public or quasi-public organization that operates within a specific geographic region to plan, coordinate, and deliver specialized services or regulatory functions separate from direct control by central government bodies.
-
D.
interregional relations
Interregional relations are the political, economic, social, and cultural interactions and institutionalized connections that occur between distinct geographic regions within or across states.
-
E.
interstate council
An interstate council is a formal collaborative body composed of representatives from multiple states or jurisdictions that coordinates policies, resolves shared issues, and facilitates joint decision-making across state boundaries.
- 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_69d85a121520819093dcce999fdefe1a |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:16 a.m.