Triple
T4821716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central American Parliament |
E107724
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | supranational legislature |
C3806
|
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: supranational legislature Context triple: [Central American Parliament, instanceOf, supranational legislature]
-
A.
supranational entity
chosen
A supranational entity is an organization or institution formed by multiple sovereign states that delegates certain decision-making powers above the national level to pursue common policies or goals.
-
B.
supranational court
A supranational court is a judicial body established by multiple states or international organizations with authority to interpret and apply shared legal norms and issue binding decisions that transcend individual national legal systems.
-
C.
supranational policy
Supranational policy is a set of rules and decisions created by an authority above individual nation-states that member countries agree to follow, often ceding some sovereignty to achieve common goals.
-
D.
supranational diplomatic office
A supranational diplomatic office is an institutional body that manages and coordinates diplomatic relations, negotiations, and policy implementation on behalf of a group of sovereign states within a higher-level international or regional organization.
-
E.
subnational legislature
A subnational legislature is a lawmaking body that operates below the national level—such as a state, provincial, or regional assembly—responsible for creating and overseeing laws and policies within its specific territorial jurisdiction.
- 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_69bd43f9efa081908314cb3e94fa1695 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:24 p.m.