Triple
T15243177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cushing, Oklahoma |
E364309
|
entity |
| Predicate | dataReportedAs |
P117738
|
FINISHED |
| Object | Cushing crude oil stocks |
—
|
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: Cushing crude oil stocks | Statement: [Cushing, Oklahoma, dataReportedAs, Cushing crude oil stocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataReportedAs Context triple: [Cushing, Oklahoma, dataReportedAs, Cushing crude oil stocks]
-
A.
dataReportedBy
Indicates that certain data has been provided, recorded, or communicated by a specific source or reporting entity.
-
B.
resultsReportedAs
Indicates that the outcomes or findings of an activity, process, or evaluation are communicated or documented in a specified form, format, or medium.
-
C.
reportedAs
Indicates that one entity has been formally reported or flagged to another entity, typically as problematic, suspicious, or noteworthy.
-
D.
reportedFor
Indicates that one entity has formally notified an authority or system about another entity’s behavior, condition, or status, typically to trigger review or action.
-
E.
reportedOn
Indicates that one entity has provided an account, description, or coverage of another entity, typically as news, documentation, or an official report.
- 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.