Triple
T24645558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xinchou Treaty |
E610098
|
entity |
| Predicate | indemnityPaymentPeriod |
P71784
|
FINISHED |
| Object | 39 years |
—
|
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: 39 years | Statement: [Xinchou Treaty, indemnityPaymentPeriod, 39 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indemnityPaymentPeriod Context triple: [Xinchou Treaty, indemnityPaymentPeriod, 39 years]
-
A.
indemnityPayableOverYears
chosen
Indicates that an indemnity obligation is to be paid out in installments over a specified number of years rather than as a single lump sum.
-
B.
policyPeriod
Indicates the time span during which a particular policy is in effect or valid.
-
C.
paymentPeriodLength
Indicates the duration or length of time that each payment period covers in a recurring payment or billing schedule.
-
D.
indemnityBasis
Indicates that one party’s obligation to compensate another for loss, damage, or liability is determined according to a specified indemnification standard or method.
-
E.
hasIndemnity
Indicates that one party provides indemnification or protection to another party against specified losses, damages, or liabilities.
- 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_69e2c4d350a481909170482bc2ce6af9 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 2:33 a.m.