Triple
T36957726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vorticons |
E914230
|
entity |
| Predicate | publisherOfGamesFeaturing |
P198833
|
FINISHED |
| Object | Apogee Software |
—
|
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: Apogee Software | Statement: [Vorticons, publisherOfGamesFeaturing, Apogee Software]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publisherOfGamesFeaturing Context triple: [Vorticons, publisherOfGamesFeaturing, Apogee Software]
-
A.
publisherOfGames
chosen
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
Indicates that one entity is the publisher responsible for releasing a particular appearance or edition of a game.
-
D.
competesInGamePublishedBy
Indicates that one entity participates as a competitor in a game that is published by another entity.
-
E.
gameProducer
Indicates that one entity is the producer responsible for creating, managing, or overseeing the development of a game associated with 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffc7b4c7f88190b6357a44e7f0940f |
completed | May 9, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69ffc755f09c8190995ca00d97336988 |
completed | May 9, 2026, 11:46 p.m. |
Created at: May 3, 2026, 4:13 p.m.