Triple
T35111452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Okinawa Reversion Agreement |
E1013298
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Japan–United States 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: Japan–United States treaty Context triple: [Okinawa Reversion Agreement, instanceOf, Japan–United States treaty]
-
A.
Act of the Diet of Japan
An Act of the Diet of Japan is a formal law enacted by Japan’s national legislature, consisting of the House of Representatives and the House of Councillors, through its prescribed legislative process.
-
B.
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.
-
C.
Hawaiian Kingdom diplomatic mission
A Hawaiian Kingdom diplomatic mission was an official delegation or permanent legation sent by the sovereign Hawaiian government to foreign states or international bodies to represent its interests, negotiate treaties, and maintain political and economic relations.
-
D.
non‑aggression pact
A non-aggression pact is a formal agreement between two or more parties in which they commit not to engage in military or hostile actions against each other, typically for a specified period.
-
E.
India–China agreement
An India–China agreement is a formal bilateral accord between the governments of India and China that outlines mutually accepted terms on specific political, economic, or security issues to manage relations and reduce conflict.
- 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_69f76dd659d08190bcdc00d37caafb62 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.