Triple
T29417020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Call of Duty: Warzone live operations |
E746052
|
entity |
| Predicate | appliesToGame |
P84357
|
FINISHED |
| Object | Call of Duty: Warzone |
—
|
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: Call of Duty: Warzone | Statement: [Call of Duty: Warzone live operations, appliesToGame, Call of Duty: Warzone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToGame Context triple: [Call of Duty: Warzone live operations, appliesToGame, Call of Duty: Warzone]
-
A.
supportsGames
Indicates that an entity is capable of running, handling, or being compatible with one or more games.
-
B.
notableGameSupport
Indicates that an entity is recognized for providing significant support or contribution to a particular game.
-
C.
associatedWithGame
chosen
Indicates that there is a relationship or connection between an entity and a particular game.
-
D.
appliesTo
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
E.
supportsGameEngine
Indicates that one entity provides compatibility, functionality, or resources necessary for the operation or integration of a particular game engine.
- 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_69f0a79f6d5c8190a350baed0157e06f |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
Created at: April 28, 2026, 3:02 p.m.