Triple
T14882990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Yandabo |
E350046
|
entity |
| Predicate | indemnityPaymentSchedule |
P71784
|
FINISHED |
| Object | four installments |
—
|
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: four installments | Statement: [Treaty of Yandabo, indemnityPaymentSchedule, four installments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indemnityPaymentSchedule Context triple: [Treaty of Yandabo, indemnityPaymentSchedule, four installments]
-
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.
creditSchedule
Indicates a planned or agreed-upon timetable for extending, using, or repaying credit between parties.
-
C.
paymentStructure
Indicates how payments are organized, scheduled, and divided between the involved parties.
-
D.
repaymentRequirement
Indicates that one party is obligated to pay back money or value to another party under specified terms or conditions.
-
E.
requiredIndemnityReceiver
Indicates that one party is obligated to provide indemnity (compensation or protection against loss) to another specified party.
- 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_69d822ee4f408190b6ac3b2fa434f0df |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded5e7c0e48190af2d68a71130585c |
completed | April 15, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69de8c1a2bcc81908f914e2e2ced65eb |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:56 a.m.