Triple
T32645877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pinocchio (2022 film) |
E834593
|
entity |
| Predicate | originalNetworkOrService |
P111224
|
FINISHED |
| Object | Disney+ |
E21464
|
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: Disney+ | Statement: [Pinocchio (2022 film), originalNetworkOrService, Disney+]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalNetworkOrService Context triple: [Pinocchio (2022 film), originalNetworkOrService, Disney+]
-
A.
originalNetwork
Indicates that one entity is the original or source network from which another network or derived entity is based or obtained.
-
B.
originalNetworkName
Indicates the name of the network from which something (e.g., data, content, or a connection) originally came.
-
C.
originalNetworkOrFormat
chosen
Indicates the network, platform, or format in which a work was first originally released or presented.
-
D.
originalNetworkPartner
Indicates that one entity is the initial or primary collaborating partner of another within a network or partnership context.
-
E.
hasNetworkOfOrigin
Indicates that an entity originates from, or is primarily associated with, a particular network or source network.
- 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_69f3492e773c81908afc10651e46cad3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a01bdacb52481909c56b0398106640e |
completed | May 11, 2026, 11:29 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a349eae8db88190951ad019006c0d2f |
completed | June 19, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_6a01bd30c8ec8190b1e54d7658b01a8d |
completed | May 11, 2026, 11:27 a.m. |
Created at: May 1, 2026, 1:07 a.m.