Triple
T32807916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wintershall Dea |
E839065
|
entity |
| Predicate | focusesOnResource |
P179495
|
FINISHED |
| Object | crude oil |
—
|
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: crude oil | Statement: [Wintershall Dea, focusesOnResource, crude oil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusesOnResource Context triple: [Wintershall Dea, focusesOnResource, crude oil]
-
A.
focusResource
chosen
Indicates that a particular resource is the primary subject of attention, emphasis, or processing within a given context or operation.
-
B.
focusesOn
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
C.
focusOf
Indicates that one entity is the primary subject, target, or center of attention, activity, or interest for another entity.
-
D.
focusesBy
Indicates that one entity directs its attention, effort, or emphasis toward another entity or specific aspect of it.
-
E.
focusesOnContentFrom
Indicates that an entity’s attention, activity, or operations are directed toward the content produced by another 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_69f3493d35208190b4351b4e85f2fa16 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 1, 2026, 1:15 a.m.