Triple
T24674119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fruitvale Oil Field |
E610928
|
entity |
| Predicate | hasRegulationFocus |
P93778
|
FINISHED |
| Object | well integrity |
—
|
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: well integrity | Statement: [Fruitvale Oil Field, hasRegulationFocus, well integrity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegulationFocus Context triple: [Fruitvale Oil Field, hasRegulationFocus, well integrity]
-
A.
hasRegulationScope
chosen
Indicates that a regulation applies to, or governs, a specified scope, domain, or area of relevance.
-
B.
hasRegulatedBy
Indicates that one entity is subject to control, governance, or rules imposed by another entity.
-
C.
hasJurisdictionFocus
Indicates that an authority’s jurisdiction is specifically directed toward or concentrated on a particular subject, area, or domain.
-
D.
hasRegulations
Indicates that one entity imposes, contains, or is associated with rules or regulatory requirements that govern the behavior or operation of another entity.
-
E.
regulatesOrIsRegulatedBy
Indicates a bidirectional regulatory relationship in which one entity controls, influences, or modulates another, or is itself controlled, influenced, or modulated by that other 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_69e2c4d5c2dc8190ac857dea25ec6ce9 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 2:57 a.m.