Triple
T36253543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial Oil |
E891864
|
entity |
| Predicate | serviceStationBrand |
P34842
|
FINISHED |
| Object | Esso |
E231050
|
NE 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: Esso | Statement: [Imperial Oil, serviceStationBrand, Esso]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceStationBrand Context triple: [Imperial Oil, serviceStationBrand, Esso]
-
A.
serviceBrand
chosen
Indicates that one entity is the brand under which a particular service is offered or marketed by another entity.
-
B.
hasServiceStationNetworkIn
Indicates that an entity operates or maintains a network of service stations within a specified geographic area or region.
-
C.
pickupBrand
Indicates that a pickup vehicle is associated with or produced by a particular brand.
-
D.
skipStopServiceBrand
Indicates that a transit service intentionally bypasses a particular stop associated with a given service brand or operator.
-
E.
catalogBrand
Indicates that a brand is associated with, or offered within, a particular catalog.
- F. None of above.
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_69f76e4599108190811532e707d6bc2c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd64bc86848190a49f451a8fc5cf1e |
completed | May 8, 2026, 4:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a396e06c19081909434ccbb106bdd5d |
completed | June 22, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69fd5ff4a648819090756d90fd195d9a |
completed | May 8, 2026, 4 a.m. |
Created at: May 3, 2026, 4:09 p.m.