Triple
T30801815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SiN (Amiga port) |
E784388
|
entity |
| Predicate | sourceGameGenre |
P53697
|
FINISHED |
| Object | first-person shooter |
—
|
LITERAL FINISHED |
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: first-person shooter | Statement: [SiN (Amiga port), sourceGameGenre, first-person shooter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceGameGenre Context triple: [SiN (Amiga port), sourceGameGenre, first-person shooter]
-
A.
gameGenreContext
chosen
Indicates the genre or type of game associated with a given game entity or gaming context.
-
B.
gameGenreDeveloped
Indicates that a particular game genre has been created, defined, or developed by a specific entity (such as a person, team, or organization).
-
C.
websiteGenre
Indicates the thematic category or type of content that a website is primarily associated with.
-
D.
gamePlatformCategory
Indicates the classification or type of platform on which a game is available or intended to be played.
-
E.
targetGenre
Indicates the genre that something is specifically aimed at, categorized under, or intended to belong to.
- 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_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 29, 2026, 8:42 p.m.