Triple
T27679580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Washington (1871) |
E697871
|
entity |
| Predicate | arbitrationAwardAmount |
P25364
|
FINISHED |
| Object | 15000000 US dollars |
—
|
LITERAL 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: 15000000 US dollars | Statement: [Treaty of Washington (1871), arbitrationAwardAmount, 15000000 US dollars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arbitrationAwardAmount Context triple: [Treaty of Washington (1871), arbitrationAwardAmount, 15000000 US dollars]
-
A.
civilJudgmentAmount
Indicates the monetary value ordered or determined in a civil court judgment between parties.
-
B.
arbitrationAwardedTo
Indicates that, as a result of an arbitration process, a decision or award has been granted in favor of a particular party.
-
C.
legalActionSettlementAmount
Indicates the monetary amount agreed upon or ordered to resolve a legal action or dispute.
-
D.
hasArbitrationAwardDate
Indicates the date on which an arbitration award was formally issued or became effective.
-
E.
awardAmount
chosen
Indicates the specific quantity or value of an award that is granted in the context of a particular awarding event or relationship.
- 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_69f6359e3d3c81909814e2f0a7fb0ea9 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 2:46 p.m.