Triple
T30538084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calso |
E777202
|
entity |
| Predicate | usedAsBrandNameFor |
P1501
|
FINISHED |
| Object | Standard Oil of California |
—
|
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: Standard Oil of California | Statement: [Calso, usedAsBrandNameFor, Standard Oil of California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsBrandNameFor Context triple: [Calso, usedAsBrandNameFor, Standard Oil of California]
-
A.
usedBrand
Indicates that an entity has utilized, applied, or operated a particular brand in some context.
-
B.
brandNameUsedIn
Indicates that a particular brand name is used or appears within a specified context, such as a product, document, or communication.
-
C.
usedBrandOf
Indicates that one entity made use of or operated an item, product, or service associated with a particular brand.
-
D.
usesBrandCharacter
Indicates that one entity employs or features another entity’s brand character (such as a mascot or branded persona) in its materials, products, or communications.
-
E.
formerBrand
chosen
Indicates that an entity was previously used or recognized as a brand for another entity but is no longer its current brand.
- 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_69f2249d183c8190b79937c1768d2163 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: April 29, 2026, 8:19 p.m.