Triple
T15243222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S&P GSCI Crude Oil Index |
E364310
|
entity |
| Predicate | derivesValueFrom |
P909
|
FINISHED |
| Object | WTI crude oil futures prices |
—
|
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: WTI crude oil futures prices | Statement: [S&P GSCI Crude Oil Index, derivesValueFrom, WTI crude oil futures prices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: derivesValueFrom Context triple: [S&P GSCI Crude Oil Index, derivesValueFrom, WTI crude oil futures prices]
-
A.
learnsValueOf
Indicates that one entity acquires or comes to understand the value, meaning, or significance of another entity.
-
B.
derivedFrom
chosen
Indicates that one entity originates, is obtained, or is developed from another source entity.
-
C.
derivedBy
Indicates that one entity is obtained, produced, or inferred from another through some transformation, process, or reasoning.
-
D.
valuedBy
Indicates that one entity is regarded as important, useful, or held in high esteem by another entity.
-
E.
derivationType
Indicates the specific manner or process by which one entity is derived or obtained from another.
- 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_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. |
Created at: April 10, 2026, 3:13 a.m.