Triple
T22531854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riverina Joint Organisation |
E557056
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | joint organisation of councils |
C4331
|
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: joint organisation of councils Context triple: [Riverina Joint Organisation, instanceOf, joint organisation of councils]
-
A.
joint organization
A joint organization is a collaborative entity formed by two or more independent parties that share resources, responsibilities, and decision-making to achieve common objectives.
-
B.
regional organisation of councils
chosen
A regional organisation of councils is a collaborative body formed by multiple local government councils within a geographic region to coordinate planning, share resources, and advocate on common regional issues.
-
C.
organ of the Council of Europe
An organ of the Council of Europe is an institutional body established by the Council’s Statute or subsequent agreements, endowed with specific functions and powers to contribute to the organization’s objectives in democracy, human rights, and the rule of law.
-
D.
inter-parliamentary organization
An inter-parliamentary organization is a cooperative body composed of members from the legislatures of multiple countries, established to promote dialogue, coordination, and collaboration on shared political, legal, and policy issues.
-
E.
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.
- 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_69e11e57483c8190b0887c4f8ff26446 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:51 p.m.