Triple
T936372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fairless Hills Coating operations |
E20203
|
entity |
| Predicate | parentCompanyTicker |
P21787
|
FINISHED |
| Object | X |
—
|
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: X | Statement: [Fairless Hills Coating operations, parentCompanyTicker, X]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentCompanyTicker Context triple: [Fairless Hills Coating operations, parentCompanyTicker, X]
-
A.
ultimateParentCompany
Indicates that one company is the highest-level controlling entity in a corporate ownership structure, with no parent company above it.
-
B.
formerParentCompany
Indicates that one entity previously served as the parent company of another but no longer holds that status.
-
C.
laterParentCompany
Indicates that one entity became the parent company of another entity at a later point in time, after some prior state or relationship.
-
D.
hasParentCompany
Indicates that one company is owned or controlled by another company that serves as its parent organization.
-
E.
memberCompany
Indicates that a company is formally part of, or affiliated as a member with, a larger organization, group, or association.
- F. None of above. chosen
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_69a493b0270c81909e6c9ce310f6aa55 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b36558588190a2a9c710073624d1 |
completed | March 1, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69a4b29b245c8190b143f28b77fede3c |
completed | March 1, 2026, 9:41 p.m. |
| PDg | Predicate description generation | batch_69a4b326d9d88190913c1a892a795707 |
completed | March 1, 2026, 9:44 p.m. |
Created at: March 1, 2026, 7:40 p.m.