Triple
T37513137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanctuary |
E932564
|
entity |
| Predicate | createdInFranchiseBy |
P118695
|
FINISHED |
| Object | Blizzard Entertainment |
—
|
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: Blizzard Entertainment | Statement: [Sanctuary, createdInFranchiseBy, Blizzard Entertainment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdInFranchiseBy Context triple: [Sanctuary, createdInFranchiseBy, Blizzard Entertainment]
-
A.
createdForFranchise
chosen
Indicates that something was created specifically to belong to, support, or be used within a particular franchise.
-
B.
createdByStudioFranchise
Indicates that a work (such as a film, show, or game) was produced as part of a specific studio-controlled franchise.
-
C.
coCreatedFranchiseWith
Indicates that two or more entities jointly created or originated the same franchise.
-
D.
isFictionallyCreatedBy
Indicates that an entity is a fictional creation authored, invented, or brought into existence within a narrative by another entity.
-
E.
filmSeriesCharacterCreatedBy
Indicates that a character in a film series was created or originated by a specific person or entity (such as a writer, creator, or studio).
- 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffebbd9bac8190b3dca4b7252a2278 |
completed | May 10, 2026, 2:21 a.m. |
| PD | Predicate disambiguation | batch_69ffe93120a08190a44bb64d052eda78 |
completed | May 10, 2026, 2:10 a.m. |
Created at: May 3, 2026, 4:17 p.m.