Triple
T32552215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disney |
E832004
|
entity |
| Predicate | platformForRelease |
P42865
|
FINISHED |
| Object | Disney+ |
—
|
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: Disney+ | Statement: [Disney, platformForRelease, Disney+]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: platformForRelease Context triple: [Disney, platformForRelease, Disney+]
-
A.
platformUsedFor
Indicates that one entity serves as the platform, medium, or environment utilized to perform, host, or support the activities of another entity.
-
B.
earlyPlatformFor
Indicates that one entity served as an initial or precursor platform, environment, or venue enabling the development, exposure, or operation of another entity.
-
C.
platformName
Indicates the name or identifier of the platform associated with the entity or action.
-
D.
consoleReleasePlatform
chosen
Indicates the specific gaming console or platform on which a particular release of a game or software is made available.
-
E.
platformAppearsOn
Indicates that a particular platform is present, visible, or available within or on another specified context, medium, or environment.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 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:02 a.m.