Triple
T30801899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gorky 17 (Amiga port) |
E784390
|
entity |
| Predicate | originalGamePublisher |
P121494
|
FINISHED |
| Object | TopWare Interactive |
—
|
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: TopWare Interactive | Statement: [Gorky 17 (Amiga port), originalGamePublisher, TopWare Interactive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalGamePublisher Context triple: [Gorky 17 (Amiga port), originalGamePublisher, TopWare Interactive]
-
A.
publisherOfGames
Indicates that an entity acts as the publisher responsible for releasing or distributing one or more games.
-
B.
gamePublisherOfWork
Indicates that one entity is the publisher responsible for releasing or distributing a particular game work.
-
C.
gamePublisherOfAppearance
chosen
Indicates that one entity is the publisher responsible for releasing a particular appearance or edition of a game.
-
D.
originalPublisherType
Indicates the type or category of the entity that first published or released the content.
-
E.
publisherStudio
Indicates that one entity serves as the publishing studio responsible for producing or releasing another entity.
- 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_69f224b3a7ec819096939414d103e31e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a006ef900148190ba52daf566882a03 |
completed | May 10, 2026, 11:41 a.m. |
| PD | Predicate disambiguation | batch_6a006c76ae748190bfe466d7d17d321e |
completed | May 10, 2026, 11:31 a.m. |
Created at: April 29, 2026, 8:42 p.m.