Triple
T34848162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perry Expedition |
E1004527
|
entity |
| Predicate | notableDocumentSigned |
P19828
|
FINISHED |
| Object | Treaty of Kanagawa |
E385588
|
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 Kanagawa | Statement: [Perry Expedition, notableDocumentSigned, Treaty of Kanagawa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDocumentSigned Context triple: [Perry Expedition, notableDocumentSigned, Treaty of Kanagawa]
-
A.
documentSignedBy
Indicates that a document has been formally signed or authorized by a specific entity.
-
B.
noteSignature
Indicates that one entity serves as a signature or identifying mark attached to a note created or associated with another entity.
-
C.
agreementSigned
chosen
Indicates that a formal agreement or contract has been officially signed and accepted by the involved parties.
-
D.
legalDocumentRatified
Indicates that a legal document has been formally approved and made officially valid by the appropriate authority or process.
-
E.
documentProclaimed
Indicates that a document formally announces, declares, or makes an official proclamation about something.
- F. None of above.
Provenance (4 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_69f76dba76f0819090643cba102c41ec |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3786cc0d3c819098bc7ca6e5baa841 |
completed | June 21, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.