Triple
T30944028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubbert peak theory |
E788338
|
entity |
| Predicate | USPeakPredictedFor |
P23826
|
FINISHED |
| Object | around 1970 |
—
|
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: around 1970 | Statement: [Hubbert peak theory, USPeakPredictedFor, around 1970]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: USPeakPredictedFor Context triple: [Hubbert peak theory, USPeakPredictedFor, around 1970]
-
A.
providesForecastFor
Indicates that one entity supplies or delivers a forecast (such as a prediction or projection) specifically concerning another entity.
-
B.
predictedIn
chosen
Indicates that something has been forecast, anticipated, or estimated to occur within or as part of a specified context, time, or situation.
-
C.
usagePeak
Indicates that the usage or consumption of something reaches its highest level or intensity during a particular time or condition.
-
D.
approximateUserPeak
Indicates that one value or event is an estimated or inferred maximum point associated with a particular user.
-
E.
pricePeakApprox
Indicates that the value or cost of something is approximately at its highest point within a given period or context.
- 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_69f224c180f88190ad177372ee02b7e2 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:53 p.m.