Triple
T2972062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Act of 1934 |
E80302
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | revision of the Hague Agreement |
C4085
|
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: revision of the Hague Agreement Context triple: [London Act of 1934, instanceOf, revision of the Hague Agreement]
-
A.
annex to international agreement
An annex to an international agreement is a supplementary document formally attached to the main treaty that provides detailed provisions, technical specifications, or additional obligations that are integral to and legally binding under the agreement.
-
B.
treaty amendment
chosen
A treaty amendment is a formal, negotiated change to an existing international agreement that modifies, adds to, or removes specific obligations or provisions for its parties.
-
C.
conciliation rules
Conciliation rules are structured guidelines or procedures designed to facilitate the amicable resolution of disputes between parties through negotiation and compromise, often with the assistance of a neutral third party.
-
D.
Annex of an international environmental agreement
An annex of an international environmental agreement is a formally attached, legally significant document that provides detailed technical, scientific, procedural, or country-specific provisions that supplement and operationalize the main treaty text.
-
E.
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.
- 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_69ad8b14ffe881908ffed62f9595c867 |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 2:58 p.m.