Triple
T11247382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IW engine |
E266240
|
entity |
| Predicate | hasVersion |
P455
|
FINISHED |
| Object | IW 6.0 |
E266240
|
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: IW 6.0 | Statement: [IW engine, hasVersion, IW 6.0]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IW 6.0 Context triple: [IW engine, hasVersion, IW 6.0]
-
A.
IW 2.0
IW 2.0 is a specific release of the IW engine software, representing an updated iteration with improvements and new features over earlier versions.
-
B.
IW
IW is the common abbreviation for Infinity Ward, a prominent video game developer best known for creating the Call of Duty franchise.
-
C.
IW engine
chosen
The IW engine is a proprietary game engine developed by Infinity Ward and used across multiple Call of Duty titles, including those created by Treyarch.
-
D.
I-640
I-640 is an auxiliary Interstate Highway that serves as a bypass route around Knoxville, Tennessee.
-
E.
I3
I3 is the IATA airline designator formerly assigned to ATA Airlines, a now-defunct U.S. low-cost carrier.
- 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_69d6aac7953c8190b82caf9d7640fdf9 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e91d1484819098ee6b2efb5316a5 |
completed | April 9, 2026, 5:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e4cc69402c8190be8785f892a41c7b |
completed | April 19, 2026, 12:36 p.m. |
Created at: April 8, 2026, 9:31 p.m.