Triple
T38383844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SADC Protocols |
E899525
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional legal instruments |
C63457
|
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 legal instruments Context triple: [SADC Protocols, instanceOf, regional legal instruments]
-
A.
regional legislation
Regional legislation comprises the laws, regulations, and legal frameworks enacted by subnational authorities (such as states, provinces, or regions) to govern matters within their territorial jurisdiction.
-
B.
private international law instrument
A private international law instrument is a legal tool—such as a treaty, regulation, or convention—that coordinates which jurisdiction’s laws and courts apply to cross-border private disputes and how foreign judgments are recognized and enforced.
-
C.
regional institutional system
A regional institutional system is a coordinated network of organizations, rules, and practices within a specific geographic area that collectively shape governance, economic activity, and social outcomes.
-
D.
SADC legal instruments
chosen
SADC legal instruments are the binding and non-binding treaties, protocols, agreements, and decisions adopted within the Southern African Development Community framework to regulate regional cooperation, integration, and governance among its member states.
-
E.
ASEAN legal instrument
An ASEAN legal instrument is a formal, collectively agreed document adopted by ASEAN member states that establishes binding or non-binding rules, commitments, or cooperative frameworks within the Association of Southeast Asian Nations.
- 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_69f76e5c9b808190b486523f5c2f817d |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:31 p.m.