Triple
T2699094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Nanking |
E58586
|
entity |
| Predicate | indemnityAmountSilverDollars |
P19678
|
FINISHED |
| Object | 21000000 |
—
|
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: 21000000 | Statement: [Treaty of Nanking, indemnityAmountSilverDollars, 21000000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indemnityAmountSilverDollars Context triple: [Treaty of Nanking, indemnityAmountSilverDollars, 21000000]
-
A.
warIndemnityAmount
chosen
Indicates the amount of financial compensation required or paid as indemnity as a result of a war or armed conflict.
-
B.
imposedWarIndemnityOn
Indicates that one party required another party to pay financial compensation as a penalty or reparation following a conflict or war.
-
C.
monetaryValue
Indicates the amount of money associated with an entity, event, or transaction.
-
D.
valueRelativeToGuilder
Indicates that something’s value is expressed in terms of, or compared relative to, the guilder currency.
-
E.
denominationDepicted
Indicates that an item visually represents or shows the monetary denomination (value) of a currency.
- 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_69ab4ac269e481909cb317d79e68b75b |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda339cf48190b9ae6b99137f005e |
completed | March 7, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69abd82062988190b4292f242ad70b2c |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.