Triple
T2495809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Call of Duty |
E52150
|
entity |
| Predicate | developer |
P73
|
FINISHED |
| Object | Treyarch |
E52872
|
NE 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: Treyarch | Statement: [Call of Duty, developer, Treyarch]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Treyarch Context triple: [Call of Duty, developer, Treyarch]
-
A.
Treyarch
chosen
Treyarch is a video game development studio best known for creating several installments in the Call of Duty franchise.
-
B.
Infinity Ward
Infinity Ward is an American video game developer best known as the original creator of the Call of Duty franchise.
-
C.
Bungie
Bungie is an American video game developer best known for creating the Halo and Destiny franchises.
-
D.
Sledgehammer Games
Sledgehammer Games is an American video game development studio best known for co-developing several titles in the Call of Duty franchise.
-
E.
ZeniMax Online Studios
ZeniMax Online Studios is a video game development studio best known for creating the massively multiplayer online role-playing game The Elder Scrolls Online.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ab4955111c8190835bf619adec21ff |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd1abd3688190b5874249e1e333bc |
completed | March 7, 2026, 7:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69af838c9c648190857a6a95dce1c258 |
completed | March 10, 2026, 2:35 a.m. |
Created at: March 6, 2026, 9:45 p.m.