Triple
T32187388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hinkley |
E822142
|
entity |
| Predicate | legalCaseSettlementAmount |
P89737
|
FINISHED |
| Object | 333 million US dollars |
—
|
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: 333 million US dollars | Statement: [Hinkley, legalCaseSettlementAmount, 333 million US dollars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalCaseSettlementAmount Context triple: [Hinkley, legalCaseSettlementAmount, 333 million US dollars]
-
A.
legalActionSettlementAmount
chosen
Indicates the monetary amount agreed upon or ordered to resolve a legal action or dispute.
-
B.
civilJudgmentAmount
Indicates the monetary value ordered or determined in a civil court judgment between parties.
-
C.
lawsuitSettlementYear
Indicates the year in which a lawsuit between parties was formally settled or resolved.
-
D.
amountInvolvedApprox
Indicates that the relationship specifies an approximate value or quantity involved in an action, event, or transaction.
-
E.
bailAmount
Indicates the specific sum of money set as security that must be paid for a person to be released from custody pending further legal proceedings.
- 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_69f3490819cc81909bae1f8ce99423c5 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fecd0a732c819097bdd3eb69b6158c |
completed | May 9, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69fecc0318d481908b5b20598a76a9fe |
completed | May 9, 2026, 5:54 a.m. |
Created at: May 1, 2026, 12:35 a.m.