Triple
T30538093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calso |
E777202
|
entity |
| Predicate | parentCompanySuccessor |
P5441
|
FINISHED |
| Object | Chevron Corporation |
—
|
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: Chevron Corporation | Statement: [Calso, parentCompanySuccessor, Chevron Corporation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentCompanySuccessor Context triple: [Calso, parentCompanySuccessor, Chevron Corporation]
-
A.
formerParentCompany
Indicates that one entity previously served as the parent company of another but no longer holds that status.
-
B.
laterParentCompany
chosen
Indicates that one entity became the parent company of another entity at a later point in time, after some prior state or relationship.
-
C.
predecessorCompany
Indicates that one company previously existed in a role or form that was succeeded or replaced by another company.
-
D.
parentCompanyAtTime
Indicates that one company is the parent (controlling) company of another during a specified time period.
-
E.
underlyingCompanyPredecessor
Indicates that one company served as a predecessor entity to another company in an underlying or foundational corporate relationship.
- 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_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: April 29, 2026, 8:19 p.m.