Triple
T6706583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belridge Oil Field |
E153020
|
entity |
| Predicate | startOfLargeScaleSteamflood |
P7527
|
FINISHED |
| Object | 1970s |
—
|
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: 1970s | Statement: [Belridge Oil Field, startOfLargeScaleSteamflood, 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfLargeScaleSteamflood Context triple: [Belridge Oil Field, startOfLargeScaleSteamflood, 1970s]
-
A.
estimatedIndustrialScale
Indicates that an entity has been assessed or projected to operate at an industrial (large-scale) level of production or activity.
-
B.
firstLargeDeployment
chosen
Indicates that this is the initial instance in which something is deployed at a large or significant scale.
-
C.
traditionalStart
Indicates that an event, process, or sequence begins in the customary or historically established way.
-
D.
hasLargeScale
Indicates that an entity operates, exists, or is implemented at a large or extensive scale relative to typical or baseline cases.
-
E.
productionScale
Indicates the relative size or volume at which something is produced, such as small-scale, medium-scale, or large-scale production.
- 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_69c68808d8d8819087369015270788fe |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d16897e48190b43eda2206b14d6a |
completed | March 27, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69c6d089c7488190a00853fb12f53b2a |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:06 p.m.