Triple
T36851493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homeworld |
E910685
|
entity |
| Predicate | originalPublisherParentCompany |
P15054
|
FINISHED |
| Object | Vivendi Universal |
E65804
|
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: Vivendi Universal | Statement: [Homeworld, originalPublisherParentCompany, Vivendi Universal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalPublisherParentCompany Context triple: [Homeworld, originalPublisherParentCompany, Vivendi Universal]
-
A.
publisherParentCompany
chosen
Indicates that one company serves as the parent (owning or controlling) company of a given publisher.
-
B.
originalPublisherType
Indicates the type or category of the entity that first published or released the content.
-
C.
formerParentCompany
Indicates that one entity previously served as the parent company of another but no longer holds that status.
-
D.
productionCompanyOfOrigin
Indicates the company that originally produced or was primarily responsible for creating a given work or product.
-
E.
parentCompanyOfOrigin
Indicates that one company is the original parent or source company from which another company was created, derived, or spun off.
- 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_69f76e8033d48190a59274f86f13be48 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3dde7c1d94819086061240db254d97 |
completed | June 26, 2026, 2:05 a.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.