Triple
T14698550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Apamea |
E345227
|
entity |
| Predicate | requiredPaymentOf |
P9211
|
FINISHED |
| Object | large war indemnity |
—
|
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: large war indemnity | Statement: [Treaty of Apamea, requiredPaymentOf, large war indemnity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiredPaymentOf Context triple: [Treaty of Apamea, requiredPaymentOf, large war indemnity]
-
A.
requiresPaymentOf
chosen
Indicates that one entity obligates another entity to provide a specified payment as a condition or requirement.
-
B.
requiresPaymentIn
Indicates that one entity must be paid in a specified currency or payment medium in order for a related action, service, or obligation to be fulfilled.
-
C.
repaymentRequirement
Indicates that one party is obligated to pay back money or value to another party under specified terms or conditions.
-
D.
conditionForPayment
Indicates the specific requirement or situation that must be satisfied before a payment is made.
-
E.
requiresPayerInformation
Indicates that the action or process cannot proceed unless specific information about the payer has been provided.
- 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_69d822e4a8c08190a155df736bb7bc13 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb604f88081908a677175045496d0 |
completed | April 14, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69de657c57ec8190ae0b9bb79a514566 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.