Triple
T23881313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 辛丑条约 |
E600207
|
entity |
| Predicate | 赔款总额 |
P19678
|
FINISHED |
| Object | 4.5亿两白银 |
—
|
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: 4.5亿两白银 | Statement: [辛丑条约, 赔款总额, 4.5亿两白银]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 赔款总额 Context triple: [辛丑条约, 赔款总额, 4.5亿两白银]
-
A.
reparationAmountPerPerson
Indicates the specific amount of reparations allocated or owed to each individual person involved.
-
B.
amountInvolvedApprox
Indicates that the relationship specifies an approximate value or quantity involved in an action, event, or transaction.
-
C.
warIndemnityAmount
chosen
Indicates the amount of financial compensation required or paid as indemnity as a result of a war or armed conflict.
-
D.
paymentAmount
Indicates the specific monetary value involved in a payment transaction between parties.
-
E.
economicDamageApprox
Indicates that one entity has caused or is associated with an estimated or approximate amount of economic damage to another entity or system.
- 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_69e295318e148190b9979d8fc02e168f |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cc05e4d48190864fc47bdffa4ca9 |
completed | April 29, 2026, 9:14 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:24 p.m.