Triple
T32030857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GenCorp |
E817952
|
entity |
| Predicate | hasCorporateParentRoleFor |
P127826
|
FINISHED |
| Object | RKO General |
E236338
|
NE 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: RKO General | Statement: [GenCorp, hasCorporateParentRoleFor, RKO General]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCorporateParentRoleFor Context triple: [GenCorp, hasCorporateParentRoleFor, RKO General]
-
A.
hasParentCompanyRole
chosen
Indicates that an entity holds a specific role or function within its parent company in a corporate hierarchy.
-
B.
hasParentCompany
Indicates that one company is owned or controlled by another company that serves as its parent organization.
-
C.
hasParentCompanyType
Indicates that an entity is associated with a parent company of a specified organizational or business type.
-
D.
hasParentCompanyBusiness
Indicates that one company operates as a business owned or controlled by another company that serves as its parent company.
-
E.
hasParentAffiliation
Indicates that an entity’s parent organization or higher-level affiliation is associated with another specified entity.
- F. None of above.
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_69f348fbc8148190b3c0f95d4772b153 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a0352b6c7dc81908f190060eb1e1857 |
completed | May 12, 2026, 4:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2eddd8845081908ba14d9585b8f5a0 |
completed | June 14, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_6a03507c37d4819091068b2ec5cacef9 |
completed | May 12, 2026, 4:08 p.m. |
Created at: May 1, 2026, 12:18 a.m.