Triple
T38156199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oloibiri |
E952892
|
entity |
| Predicate | oilDiscoveryCompany |
P190149
|
FINISHED |
| Object | Shell Darcy |
—
|
NE NERFINISHED |
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: Shell Darcy | Statement: [Oloibiri, oilDiscoveryCompany, Shell Darcy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oilDiscoveryCompany Context triple: [Oloibiri, oilDiscoveryCompany, Shell Darcy]
-
A.
hasOnshoreOilAndGasProduction
Indicates that an entity engages in or possesses facilities for extracting oil and/or natural gas from onshore (land-based) fields.
-
B.
discoveredAsOilField
Indicates that a location or resource was identified and recognized specifically as an oil field.
-
C.
hydrocarbonExplorationRights
Indicates that an entity holds the legal authority to explore a specified area for hydrocarbon resources such as oil and natural gas.
-
D.
isOilIndustryHub
Indicates that a location serves as a central focal point for activities, infrastructure, and operations related to the oil industry.
-
E.
hydrocarbonExploitationRights
Indicates that an entity holds legal rights to explore for, extract, and commercially exploit hydrocarbon resources (such as oil and gas) in a specified area.
- F. None of above. chosen
Provenance (4 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_69f76f0a67f4819080c492f61d688fcc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcb089a8f881909aa9e722babd43f7 |
completed | May 7, 2026, 3:32 p.m. |
| PD | Predicate disambiguation | batch_69fc45666c5c8190913bd632ac0e5b84 |
completed | May 7, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69fcb088aac481909db90804faff315f |
completed | May 7, 2026, 3:32 p.m. |
Created at: May 3, 2026, 4:21 p.m.