Triple
T1274574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of The Hague (1795) |
E15783
|
entity |
| Predicate | imposedPayment |
P7925
|
FINISHED |
| Object | large war indemnity on Batavian Republic |
—
|
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 on Batavian Republic | Statement: [Treaty of The Hague (1795), imposedPayment, large war indemnity on Batavian Republic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: imposedPayment Context triple: [Treaty of The Hague (1795), imposedPayment, large war indemnity on Batavian Republic]
-
A.
paidBy
Indicates that a payment or financial obligation is made or settled by the specified entity.
-
B.
paymentAmount
Indicates the specific monetary value involved in a payment transaction between parties.
-
C.
imposedOn
Indicates that one party enforces, applies, or places a requirement, burden, or constraint onto another party or entity.
-
D.
requiresPaymentOf
Indicates that one entity obligates another entity to provide a specified payment as a condition or requirement.
-
E.
imposes
chosen
Indicates that one entity enforces, applies, or places a rule, condition, burden, or obligation upon another entity.
- 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_69a4935a94308190bb92555b79032824 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4c31602b8819087a57e8d390cae7a |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4bee0be808190a8ccac6a41851fdd |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.