Triple
T34792956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shreck's Department Store |
E1002994
|
entity |
| Predicate | publisherStudio |
P199825
|
FINISHED |
| Object | Warner Bros. |
—
|
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: Warner Bros. | Statement: [Shreck's Department Store, publisherStudio, Warner Bros.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publisherStudio Context triple: [Shreck's Department Store, publisherStudio, Warner Bros.]
-
A.
publisherType
Indicates the classification or category of a publisher in relation to a published work or entity.
-
B.
publisherParentCompany
Indicates that one company serves as the parent (owning or controlling) company of a given publisher.
-
C.
publisherProgram
Indicates a program or initiative operated by a publisher that manages or governs its relationships, activities, or offerings with participating entities.
-
D.
publisherDivision
Indicates the organizational subdivision or imprint within a publishing company that is responsible for producing or managing the associated work.
-
E.
publisherOfGames
Indicates that an entity acts as the publisher responsible for releasing or distributing one or more games.
- F. None of above. chosen
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_69f76db47d408190a24fc7164439ea2d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ff59b33a38819086cc9aa19b81748b |
completed | May 9, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69ff587758f88190a39c2164341dc554 |
completed | May 9, 2026, 3:53 p.m. |
| PDg | Predicate description generation | batch_69ff59b1e2ac8190bb65529e9dbbb178 |
completed | May 9, 2026, 3:58 p.m. |
Created at: May 3, 2026, 3:59 p.m.