Triple
T21777287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inter-American Convention on the Law Applicable to International Contracts |
E537615
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | conflict of laws instrument |
C23187
|
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: conflict of laws instrument Context triple: [Inter-American Convention on the Law Applicable to International Contracts, instanceOf, conflict of laws instrument]
-
A.
type of legal instrument
A type of legal instrument is a category of formally recognized documents or mechanisms, such as contracts, statutes, or wills, that create, modify, or extinguish legal rights and obligations.
-
B.
legally binding international instrument
chosen
A legally binding international instrument is a formal agreement between states or international actors that creates enforceable rights and obligations under international law.
-
C.
law of the sea instrument
A law of the sea instrument is a formal legal document—such as a treaty, convention, or agreement—that establishes rules and principles governing the use, rights, and responsibilities of states and other actors in maritime spaces.
-
D.
legal jurisdiction
A legal jurisdiction is a defined geographic area or subject-matter domain within which a particular court or governmental authority has the power to create, interpret, and enforce laws.
-
E.
arbitration legislation
Arbitration legislation is the body of laws and regulations that governs how disputes are resolved through arbitration instead of traditional court litigation, defining procedures, rights, and enforcement of arbitral awards.
- 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_69e0c470759c819094a215757113562b |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:51 p.m.