Triple
T21208455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilmington Oil Field |
E522651
|
entity |
| Predicate | hasProductionWells |
P143555
|
FINISHED |
| Object | hundreds of wells historically |
—
|
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: hundreds of wells historically | Statement: [Wilmington Oil Field, hasProductionWells, hundreds of wells historically]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProductionWells Context triple: [Wilmington Oil Field, hasProductionWells, hundreds of wells historically]
-
A.
hasNearbyOilAndGasFields
Indicates that an entity is located close to one or more oil and gas extraction fields.
-
B.
hasUnconventionalProduction
Indicates that something is created or produced using methods, processes, or practices that deviate from standard or traditional approaches.
-
C.
containsOilField
Indicates that one entity geographically includes or encompasses an oil field within its boundaries.
-
D.
hasNearbyOilField
Indicates that an entity is located close to or in the vicinity of an oil field.
-
E.
hasProductionFacilitiesIn
Indicates that an entity operates or owns production facilities located within a specified geographic area or jurisdiction.
- 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_69e0b5112d8881909510b2dcdc93106d |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73436eb4c819082e05caf1ba52672 |
completed | April 21, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69e5f6094e3c81909ee9699e00d371f7 |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5fa92a2448190896c022dd27511ad |
completed | April 20, 2026, 10:06 a.m. |
Created at: April 16, 2026, 3:25 p.m.