Triple
T22029421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lump-Sum Death Payment |
E544046
|
entity |
| Predicate | amountType |
P9758
|
FINISHED |
| Object | fixed statutory amount |
—
|
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: fixed statutory amount | Statement: [Lump-Sum Death Payment, amountType, fixed statutory amount]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: amountType Context triple: [Lump-Sum Death Payment, amountType, fixed statutory amount]
-
A.
quantityType
chosen
Indicates that one entity is the type or category of quantity to which another entity (a specific measured or measurable amount) belongs.
-
B.
denominationType
Indicates the specific category or kind of denomination associated with an entity, such as its type within a broader classification of denominations.
-
C.
monetaryValue
Indicates the amount of money associated with an entity, event, or transaction.
-
D.
calculationType
Indicates the specific method, formula, or approach used to perform a calculation in the described relationship.
-
E.
currencyGiven
Indicates that one entity transfers or provides money or a monetary unit to 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_69e11e2f98c8819083e11eab90942a78 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127ebf6d48190b84e7a45bbf9049c |
completed | April 28, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69e6f63b0d048190b241622759aab9de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:24 p.m.