Triple
T38463288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seoul Dynasty |
E912502
|
entity |
| Predicate | competesInGamePublishedBy |
P194161
|
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: [Seoul Dynasty, competesInGamePublishedBy, Blizzard Entertainment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competesInGamePublishedBy Context triple: [Seoul Dynasty, competesInGamePublishedBy, Blizzard Entertainment]
-
A.
gamePublisherOfAppearance
Indicates that one entity is the publisher responsible for releasing a particular appearance or edition of a game.
-
B.
gamePublisherOfWork
Indicates that one entity is the publisher responsible for releasing or distributing a particular game work.
-
C.
publishesGame
Indicates that a publisher releases or makes a game available to the public.
-
D.
gameProducer
Indicates that one entity is the producer responsible for creating, managing, or overseeing the development of a game associated with another entity.
-
E.
relatedGame
Indicates that one game has a notable connection or association with another game, such as shared content, themes, or series.
- 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_69f76e861d8c81908559031dc66e3c15 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd64bc86848190a49f451a8fc5cf1e |
completed | May 8, 2026, 4:21 a.m. |
| PD | Predicate disambiguation | batch_69fd5ff4a648819090756d90fd195d9a |
completed | May 8, 2026, 4 a.m. |
| PDg | Predicate description generation | batch_69fd64bb345c819096a35c72784a8ce3 |
completed | May 8, 2026, 4:21 a.m. |
Created at: May 3, 2026, 4:31 p.m.