Triple
T8204111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nagoya–Kuala Lumpur Supplementary Protocol on Liability and Redress |
E191647
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | supplementary protocol |
C21515
|
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: supplementary protocol Context triple: [Nagoya–Kuala Lumpur Supplementary Protocol on Liability and Redress, instanceOf, supplementary protocol]
-
A.
additional protocol
chosen
An additional protocol is a supplementary legal instrument that amends, clarifies, or expands the provisions of an existing treaty or agreement without replacing it.
-
B.
optional protocol
An optional protocol is a set of behaviors or methods that a class or object may implement but is not required to, allowing flexible and partial conformance to a shared interface.
-
C.
experimental procedure
An experimental procedure is a structured, step-by-step set of methods and conditions designed to systematically test a hypothesis or investigate a research question.
-
D.
supplementary Hour
A supplementary Hour is an additional, non-standard time period added beyond the regular schedule to accommodate overflow activities, special events, or extended operations.
-
E.
transitional provision
A transitional provision is a legal rule that governs how new laws or regulations apply to situations, rights, or obligations that originated under previous legal frameworks during a changeover period.
- 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_69ca82c7f3e08190857bf1fc63b2a10c |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:43 p.m.