Triple
T30944027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubbert peak theory |
E788338
|
entity |
| Predicate | predictionMadeIn |
P23826
|
FINISHED |
| Object | 1956 |
—
|
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: 1956 | Statement: [Hubbert peak theory, predictionMadeIn, 1956]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predictionMadeIn Context triple: [Hubbert peak theory, predictionMadeIn, 1956]
-
A.
predictedIn
chosen
Indicates that something has been forecast, anticipated, or estimated to occur within or as part of a specified context, time, or situation.
-
B.
predictionBy
Indicates that one entity serves as the source or author of a prediction made about another entity or outcome.
-
C.
predictionType
Indicates the kind or category of prediction being made about an entity or event.
-
D.
historicallyPredicted
Indicates that, based on historical data or past patterns, one entity was used to forecast or anticipate the behavior, state, or outcome of another entity.
-
E.
predictionInterpretation
Indicates that one entity represents an explanation, meaning, or understanding of a prediction made about another entity.
- 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.