Triple
T30944029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubbert peak theory |
E788338
|
entity |
| Predicate | USPeakObserved |
P4936
|
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, USPeakObserved, around 1970]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: USPeakObserved Context triple: [Hubbert peak theory, USPeakObserved, around 1970]
-
A.
historicalPeak
chosen
Indicates that the related value or state represents the highest level ever reached by something within a historical or recorded time frame.
-
B.
areaPeak
Indicates that a specified location or region is the highest point (peak) within a given area or spatial extent.
-
C.
highestPointWestOf
Indicates that one location is the highest-elevation point among all locations situated to the west of a specified reference location.
-
D.
highestPeaksLocatedIn
Indicates that the specified highest mountain peaks are geographically situated within the given location or region.
-
E.
notableWeather
Indicates that a location experiences weather conditions that are significant, unusual, or noteworthy in some way.
- 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_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 8:53 p.m.