Triple
T26596095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chevron Canada |
E667493
|
entity |
| Predicate | hasParentHeadquartersLocation |
P11921
|
FINISHED |
| Object | San Ramon, 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: San Ramon, California | Statement: [Chevron Canada, hasParentHeadquartersLocation, San Ramon, California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentHeadquartersLocation Context triple: [Chevron Canada, hasParentHeadquartersLocation, San Ramon, California]
-
A.
hasParentCompanyHeadquarters
chosen
Indicates that a company’s parent organization has its main headquarters located at a specified place.
-
B.
hasHigherHeadquarters
Indicates that one organizational unit serves as the superior or parent headquarters overseeing another unit.
-
C.
hasOrganizationHeadquarters
Indicates that an organization’s main administrative or operational center is located at a specific place.
-
D.
headquartersLocation
Indicates the place where an organization’s main administrative center or principal office is located.
-
E.
hasManufacturerHeadquartersIn
Indicates that the location specified is the place where the manufacturer’s main headquarters is situated.
- 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_69ee9cfc385081909ac9ae178030a06e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 27, 2026, 2:10 a.m.