Triple
T5899912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Price |
E131194
|
entity |
| Predicate | signedContractValue |
P48293
|
FINISHED |
| Object | 217 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: 217 million US dollars | Statement: [David Price, signedContractValue, 217 million US dollars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signedContractValue Context triple: [David Price, signedContractValue, 217 million US dollars]
-
A.
contractValue
chosen
Indicates the monetary worth or agreed-upon financial amount specified in a contract between parties.
-
B.
signedLongTermContractWith
Indicates that one entity has formally entered into a binding long-term contractual agreement with another entity.
-
C.
agreementSigned
Indicates that a formal agreement or contract has been officially signed and accepted by the involved parties.
-
D.
signedFirstProfessionalContractWith
Indicates that an entity has formally entered into their first professional contractual agreement with another entity.
-
E.
conventionSigned
Indicates that an entity has formally agreed to and signed a specific convention or treaty.
- 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_69c0085864a88190a569c05ff7d65f29 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0400f1af881908d376ea4793f6dea |
completed | March 22, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69c0334dc8248190b7394dcece362d52 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:58 p.m.