Triple
T38463047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BlizzCon 2013 |
E912497
|
entity |
| Predicate | announcedTitle |
P8467
|
FINISHED |
| Object | Heroes of the Storm |
—
|
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: Heroes of the Storm | Statement: [BlizzCon 2013, announcedTitle, Heroes of the Storm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: announcedTitle Context triple: [BlizzCon 2013, announcedTitle, Heroes of the Storm]
-
A.
announcedAs
chosen
Indicates that one entity is publicly presented, declared, or introduced in a specified role, name, or capacity by another entity.
-
B.
announcedThat
Indicates that one entity publicly communicated or declared a specific fact, decision, or piece of information about another entity or situation.
-
C.
announcedWith
Indicates that one entity was publicly revealed, declared, or introduced at the same time as, and in explicit association with, another entity.
-
D.
announcedFor
Indicates that one entity has been publicly declared or made known in connection with, or on behalf of, another entity.
-
E.
announcedEntry
Indicates that an entity has publicly communicated or declared the initiation or presence of another entity or event.
- 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_69f76e861d8c81908559031dc66e3c15 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:31 p.m.