Triple
T36916001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russia–Japan relations |
E913046
|
entity |
| Predicate | firstMajorTreaty |
P205634
|
FINISHED |
| Object | Treaty of Shimoda |
E150549
|
NE FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Treaty of Shimoda | Statement: [Russia–Japan relations, firstMajorTreaty, Treaty of Shimoda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstMajorTreaty Context triple: [Russia–Japan relations, firstMajorTreaty, Treaty of Shimoda]
-
A.
signedMajorTreaty
Indicates that an entity formally entered into and approved a significant, binding treaty with another party or parties.
-
B.
treatyOf
Indicates a formal agreement or pact established between entities, typically states or organizations, defining their mutual obligations or terms.
-
C.
colonialTreaty
Indicates a formal agreement imposed or established between a colonial power and a territory or population under its colonial influence or control.
-
D.
historicalTreaty
Indicates that a formal agreement or pact was established between entities at some point in the past.
-
E.
treatyOrEvent
Indicates that there exists a formal agreement or significant occurrence involving the related entities.
- F. None of above. chosen
Provenance (5 batches)
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_69f76e885b848190bad82c87e9525486 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e162c27d48190be137eed05ddf08d |
completed | June 26, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:13 p.m.