Triple
T24560823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aker BP |
E607645
|
entity |
| Predicate | hasMainCustomers |
P33576
|
FINISHED |
| Object | global energy markets |
—
|
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: global energy markets | Statement: [Aker BP, hasMainCustomers, global energy markets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainCustomers Context triple: [Aker BP, hasMainCustomers, global energy markets]
-
A.
hasCustomers
chosen
Indicates that an entity maintains a business relationship in which other entities purchase or receive its goods or services as customers.
-
B.
hasCustomerServices
Indicates that an entity provides or is associated with one or more customer service functions or offerings.
-
C.
majorCustomer
Indicates that one entity is a primary or high-value customer of another entity, typically contributing a significant portion of business or revenue.
-
D.
hasCustomerIndustry
Indicates that a customer is associated with or operates within a particular industry or sector.
-
E.
hasMainHost
Indicates that one entity serves as the primary or principal host for 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_69e2c4cc35a48190990b7571bc086df8 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8f63a348190a3c9fd96e3ad80b0 |
completed | April 30, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:28 a.m.