Triple
T27679595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Washington (1871) |
E697871
|
entity |
| Predicate | USPlenipotentiary |
P158474
|
FINISHED |
| Object | Hamilton Fish |
—
|
NE NERFINISHED |
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: Hamilton Fish | Statement: [Treaty of Washington (1871), USPlenipotentiary, Hamilton Fish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: USPlenipotentiary Context triple: [Treaty of Washington (1871), USPlenipotentiary, Hamilton Fish]
-
A.
diplomaticRole
Indicates that an entity holds or has held an official diplomatic position or function in relation to another entity or context.
-
B.
seatOfPlenipotentiaryRepresentative
Indicates the location or institution that serves as the official base or office for a plenipotentiary representative.
-
C.
firstSecretaryOfState
Indicates that the subject is the first person to have held the position of Secretary of State for the specified entity.
-
D.
typeOfDiplomaticRole
Indicates the specific kind or category of diplomatic position or function that an entity holds in relation to another.
-
E.
signatoryDiplomat
chosen
Indicates that a diplomat is an official signatory to an agreement, treaty, or formal document.
- F. None of above.
Provenance (3 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_69ef590d458c81909583290c3cd0478b |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6353654188190915266b42fb1885a |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:46 p.m.