Triple
T28049974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 日本取引所グループ |
E708793
|
entity |
| Predicate | 親会社形態 |
P117303
|
FINISHED |
| Object | 持株会社制 |
—
|
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: 持株会社制 | Statement: [日本取引所グループ, 親会社形態, 持株会社制]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 親会社形態 Context triple: [日本取引所グループ, 親会社形態, 持株会社制]
-
A.
hasParentCompanyLegalForm
chosen
Indicates that an entity’s parent company possesses a specific legal form or legal organizational type.
-
B.
hasParentCompanyType
Indicates that an entity is associated with a parent company of a specified organizational or business type.
-
C.
corporateStructure
Indicates how entities are organized, controlled, and related within a corporate hierarchy or ownership structure.
-
D.
ultimateParentCompany
Indicates that one company is the highest-level controlling entity in a corporate ownership structure, with no parent company above it.
-
E.
subsidiaryOrJointVenture
Indicates that one organization is either a subsidiary of, or a jointly owned venture with, another 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_69ef9b6df9f48190bbb971d02cbe1b65 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f63fd88d408190af30ebec8469b050 |
completed | May 2, 2026, 6:18 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 8:32 p.m.