Triple
T24529589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Poso Oil Field |
E606764
|
entity |
| Predicate | isMajorFieldIn |
P81006
|
FINISHED |
| Object | Kern County oil production |
—
|
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: Kern County oil production | Statement: [Mount Poso Oil Field, isMajorFieldIn, Kern County oil production]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorFieldIn Context triple: [Mount Poso Oil Field, isMajorFieldIn, Kern County oil production]
-
A.
isMajorFieldWithin
Indicates that one academic or professional major field is contained within or is a specialization of a broader field.
-
B.
hasMajorField
Indicates that an entity (such as a person or student) has a primary area of academic or professional specialization.
-
C.
isMajorFor
Indicates that one entity serves as the primary field of academic specialization (major) for another entity, typically a student.
-
D.
isMajorSeeWithin
chosen
Indicates that one entity is the primary or most significant location or area encompassed within the boundaries of another entity.
-
E.
isMajorBaseIn
Indicates that a location serves as a primary or central base of operations within a specified area or organization.
- 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_69e2c4c90c848190b23c4303620dcaaf |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b0ca8081908d931aec560eae56 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:25 a.m.