Triple
T121084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations Convention on the Law of the Sea |
E2445
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | law of the sea treaty |
C566
|
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: law of the sea treaty Context triple: [United Nations Convention on the Law of the Sea, instanceOf, law of the sea treaty]
-
A.
treaty
chosen
A treaty is a formal, legally binding agreement between two or more sovereign states or international entities that defines their mutual rights, obligations, and commitments.
-
B.
article of an international treaty
An article of an international treaty is a distinct, numbered provision that sets out specific rights, obligations, definitions, or procedures agreed upon by the treaty’s parties.
-
C.
founding treaty
A founding treaty is a formal, binding international agreement that establishes, constitutes, and defines the core structures, powers, and purposes of an international organization or political union.
-
D.
subject of international law
A subject of international law is an entity recognized by the international legal system as having rights, duties, and the capacity to act on the international plane, such as states, international organizations, and in some cases individuals.
-
E.
sovereign subject of international law
A sovereign subject of international law is an entity, typically a state, that possesses full legal personality and capacity to hold rights, assume obligations, and participate independently in the international legal order.
- 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_69a2506c5428819085c28a8884790e29 |
completed | Feb. 28, 2026, 2:18 a.m. |
Created at: Feb. 28, 2026, 2:24 a.m.