Triple
T8552320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Advanced Entertainment System |
E202471
|
entity |
| Predicate | notableGameGenre |
P53697
|
FINISHED |
| Object | fighting game |
—
|
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: fighting game | Statement: [Advanced Entertainment System, notableGameGenre, fighting game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableGameGenre Context triple: [Advanced Entertainment System, notableGameGenre, fighting game]
-
A.
notableGameType
Indicates that a game is of a particular type or category for which the subject is especially well known or notable.
-
B.
gameGenreContext
chosen
Indicates the genre or type of game associated with a given game entity or gaming context.
-
C.
notableGame
Indicates that a particular game is especially significant, prominent, or well-known in relation to the associated entity.
-
D.
notableGameEngineFor
Indicates that a particular game engine is especially recognized or significant for developing or powering a given game or set of games.
-
E.
websiteGenre
Indicates the thematic category or type of content that a website is primarily associated with.
- 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_69ca832610e08190b3b6c6cd2c250255 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe8882704819094b688d46169433a |
completed | March 31, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69cbd113e05c81908f4f3fc1b5925164 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:19 p.m.