Triple
T20567631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Utusan Daerah in the MPR |
E505004
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional representative group |
C43268
|
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: regional representative group Context triple: [Utusan Daerah in the MPR, instanceOf, regional representative group]
-
A.
regional organisation
A regional organisation is an entity formed by multiple countries or territories within a specific geographic area to coordinate policies, promote cooperation, and address shared economic, political, social, or security issues.
-
B.
regional electoral body
A regional electoral body is an organization responsible for administering, supervising, and ensuring the integrity of elections within a specific subnational geographic area.
-
C.
regional NRM group
A regional NRM group is an organization that coordinates and supports natural resource management activities across a defined geographic area, working with communities, governments, and stakeholders to sustainably manage land, water, and biodiversity.
-
D.
United Nations Regional Group
A United Nations Regional Group is a coalition of member states organized by geographic region to coordinate positions, facilitate negotiations, and allocate seats in UN bodies and committees.
-
E.
regional cooperation bloc
A regional cooperation bloc is an alliance of neighboring countries that coordinate policies and collaborate on economic, political, or security issues to advance shared regional interests.
- 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_69e0b4b6587c8190aee63dc7cff244ea |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:39 a.m.