Triple
T3521786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WTI crude oil futures |
E74438
|
entity |
| Predicate | standardContractSize |
P15868
|
FINISHED |
| Object | 1000 barrels |
—
|
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 | Statement: [WTI crude oil futures, standardContractSize, 1000 barrels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardContractSize Context triple: [WTI crude oil futures, standardContractSize, 1000 barrels]
-
A.
hasLotSize
Indicates that an entity possesses a specific amount or extent of physical area, typically referring to the size of a parcel of land or property lot.
-
B.
typicalUnitSize
Indicates the standard or most common size or quantity in which something is typically measured, packaged, or used.
-
C.
marginType
Indicates the type or category of margin applied in a given context, such as financial, layout, or safety margin.
-
D.
minimumUnitSize
Indicates that there is a smallest allowable or defined size or quantity for the unit involved in the relationship.
-
E.
contractMultiplier
chosen
Indicates the standardized number of underlying units (e.g., shares, commodities) that one contract represents in a derivatives or futures agreement.
- 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_69ad85d0c5488190a3d8e02ebd01a1aa |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc4dd6d48190a5a3f4b86c82b86c |
completed | March 8, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69adae10689c8190b7dc6d7daa8295b6 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:19 p.m.