Triple
T9001094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony Life |
E215039
|
entity |
| Predicate | hasSubsidiaryRoleIn |
P28882
|
FINISHED |
| Object | Sony Financial Group life insurance operations |
—
|
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: Sony Financial Group life insurance operations | Statement: [Sony Life, hasSubsidiaryRoleIn, Sony Financial Group life insurance operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubsidiaryRoleIn Context triple: [Sony Life, hasSubsidiaryRoleIn, Sony Financial Group life insurance operations]
-
A.
hasSubrole
Indicates that one role functions as a more specific, subordinate, or specialized version of another broader role.
-
B.
hasSubsidiaryRoleInGroup
chosen
Indicates that an entity holds a secondary or supporting role within a specified group.
-
C.
hasSubsidiaryLabel
Indicates that one entity is identified as a subsidiary or subordinate organization of another entity.
-
D.
usedBySubsidiaryOf
Indicates that something is used by an entity that is a subsidiary of another organization.
-
E.
coreSubsidiaryOf
Indicates that one entity is a primary or central subsidiary that is owned or controlled by another entity.
- 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_69ca83a12d648190b1e4fe11e8a31890 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6954bb1881908d004a26ba7fe360 |
completed | April 1, 2026, 12:39 a.m. |
| PD | Predicate disambiguation | batch_69cc5edd6cb48190b4fc6d6ca0418056 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:05 p.m.