Triple
T12160206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Call of Duty: Modern Warfare II (2022) |
E289682
|
entity |
| Predicate | supportsWeaponTuning |
P103269
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Call of Duty: Modern Warfare II (2022), supportsWeaponTuning, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsWeaponTuning Context triple: [Call of Duty: Modern Warfare II (2022), supportsWeaponTuning, yes]
-
A.
supportsWeapon
Indicates that one entity is capable of accommodating, using, or being compatible with a specified weapon.
-
B.
tuning
Indicates the adjustment or calibration of something’s parameters or settings to achieve desired performance or behavior.
-
C.
weaponFeature
Indicates that one entity is a characteristic, attribute, or functional aspect of a weapon.
-
D.
equipmentOption
Indicates that a particular piece or configuration of equipment is available or selected as an option in a given context.
-
E.
weaponCapability
Indicates that one entity has the ability to use, deploy, or function as a weapon against another entity or target.
- F. None of above. chosen
Provenance (4 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_69d6ab4d6c00819095a9a7c35de83cfb |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d915d7109481908bf5fe512bba3c89 |
completed | April 10, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69d9150c18148190bf8152189c0e5fca |
completed | April 10, 2026, 3:19 p.m. |
| PDg | Predicate description generation | batch_69d915d58ab881908b5b7901990308a4 |
completed | April 10, 2026, 3:23 p.m. |
Created at: April 8, 2026, 9:50 p.m.