Triple
T31242798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony Pictures email leak |
E796606
|
entity |
| Predicate | parentCompanyOfTarget |
P20316
|
FINISHED |
| Object | Sony 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: Sony Corporation | Statement: [Sony Pictures email leak, parentCompanyOfTarget, Sony Corporation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentCompanyOfTarget Context triple: [Sony Pictures email leak, parentCompanyOfTarget, Sony Corporation]
-
A.
ultimateParentCompany
Indicates that one company is the highest-level controlling entity in a corporate ownership structure, with no parent company above it.
-
B.
parentCompanyOfPartner
Indicates that one entity is the parent company of another entity that is identified as a partner.
-
C.
parentCompanyOfProvider
Indicates that one company serves as the parent company of a given provider entity.
-
D.
parentCompanyOfLicensee
Indicates that one entity is the parent company of another entity that holds a license.
-
E.
hasParentCompany
chosen
Indicates that one company is owned or controlled by another company that serves as its parent organization.
- 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_69f224db69ac81909a370adad6a7ac7c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: April 29, 2026, 9:11 p.m.