Triple
T32647496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disney Digital |
E834632
|
entity |
| Predicate | brandOwnerSubsidiary |
P125763
|
FINISHED |
| Object | Walt Disney Studios |
—
|
NE NERFINISHED |
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: Walt Disney Studios | Statement: [Disney Digital, brandOwnerSubsidiary, Walt Disney Studios]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brandOwnerSubsidiary Context triple: [Disney Digital, brandOwnerSubsidiary, Walt Disney Studios]
-
A.
manufacturerSubsidiaryOf
Indicates that a manufacturer operates as a subsidiary company that is owned or controlled by another entity.
-
B.
parentBrandOwner
chosen
Indicates that one entity is the owning parent company or brand proprietor of another brand entity.
-
C.
brandOwnerCurrentName
Indicates that the subject entity is the current legal or official name of the owner of the specified brand.
-
D.
parentBrand
Indicates that one brand is the overarching or owning brand from which another brand is derived or subordinated.
-
E.
successorBrandOwner
Indicates that one brand owner has taken over ownership or control of a brand from a previous brand owner, acting as its legal or commercial successor.
- 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_69f3492e773c81908afc10651e46cad3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:07 a.m.