Triple
T15243096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CL |
E364308
|
entity |
| Predicate | contractSize |
P117733
|
FINISHED |
| Object | 1000 barrels of crude oil |
—
|
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: 1000 barrels of crude oil | Statement: [CL, contractSize, 1000 barrels of crude oil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contractSize Context triple: [CL, contractSize, 1000 barrels of crude oil]
-
A.
contractSizeBasedOn
Indicates that the size or quantity specified in a contract is determined or calculated based on another referenced factor or entity.
-
B.
contractValue
Indicates the monetary worth or agreed-upon financial amount specified in a contract between parties.
-
C.
signedContractLength
Indicates the duration or term length specified in a contract that has been formally signed between parties.
-
D.
typeOfContract
Indicates the specific kind or category of contractual agreement that applies between the related entities.
-
E.
contractUnit
Indicates that one entity serves as a contractual unit or party within a contract relationship involving another entity.
- F. None of above. chosen
Provenance (4 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007dcc33081908545ea1a1d2c19fe |
completed | April 15, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69deca899d5c8190be4a7c71e1683c69 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2ca6148190967c319728ec3661 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:13 a.m.