Triple
T33844578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TV Tokyo Holdings (partial stake) |
E867442
|
entity |
| Predicate | ownershipSubject |
P347
|
FINISHED |
| Object | shares of TV Tokyo Holdings Corporation |
—
|
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: shares of TV Tokyo Holdings Corporation | Statement: [TV Tokyo Holdings (partial stake), ownershipSubject, shares of TV Tokyo Holdings Corporation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownershipSubject Context triple: [TV Tokyo Holdings (partial stake), ownershipSubject, shares of TV Tokyo Holdings Corporation]
-
A.
ownershipConfers
Indicates that possessing or owning something grants the owner certain rights, powers, or privileges over it.
-
B.
ownedBy
chosen
Indicates that one entity possesses legal or rightful ownership of another entity.
-
C.
ownershipRecordedBy
Indicates that the fact or status of ownership of an entity is documented or registered by a particular agent or system.
-
D.
ownershipSince
Indicates the point in time from which an entity has continuously owned another entity.
-
E.
ownershipType
Indicates the specific nature or category of the ownership relationship that one entity holds over another.
- 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_69f349937b648190a34ada70f6a2b534 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 1, 2026, 1:47 a.m.