Triple
T11563250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Call of Duty: Infinite Warfare (support studio) |
E274193
|
entity |
| Predicate | genreOfSupportedGame |
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: [Call of Duty: Infinite Warfare (support studio), genreOfSupportedGame, first-person shooter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genreOfSupportedGame Context triple: [Call of Duty: Infinite Warfare (support studio), genreOfSupportedGame, first-person shooter]
-
A.
includesGameType
Indicates that one entity contains or supports a particular type or category of game.
-
B.
gameGenreContext
chosen
Indicates the genre or type of game associated with a given game entity or gaming context.
-
C.
notableGameSupport
Indicates that an entity is recognized for providing significant support or contribution to a particular game.
-
D.
hasGameType
Indicates that an entity (such as a game or match) is associated with a specific category or type of game.
-
E.
notableGameType
Indicates that a game is of a particular type or category for which the subject is especially well known or notable.
- 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_69d6aae5ac3c81908d2b0a3a665665b2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88dd2016481909b33848af3d1d6c1 |
completed | April 10, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69d85dc3fc2c8190bed7e2111301a77c |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:37 p.m.