Triple
T37011767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Call of Duty 2: Big Red One |
E915968
|
entity |
| Predicate | hasWeapons |
P6014
|
FINISHED |
| Object | World War II-era firearms |
—
|
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: World War II-era firearms | Statement: [Call of Duty 2: Big Red One, hasWeapons, World War II-era firearms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWeapons Context triple: [Call of Duty 2: Big Red One, hasWeapons, World War II-era firearms]
-
A.
weaponryCarried
Indicates that one entity is carrying or equipped with a weapon or set of weapons in relation to another entity or context.
-
B.
hasWeaponType
chosen
Indicates that an entity is associated with or equipped with a specific type or category of weapon.
-
C.
hasWeaponOption
Indicates that an entity has a particular weapon available as a selectable or usable option.
-
D.
armedBy
Indicates that one entity is supplied with weapons, equipment, or armaments by another entity.
-
E.
usedWeapon
Indicates that an entity employed a specific weapon as the means or tool to carry out an action or event.
- 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_69f76e90ed548190b187d2475f5c807d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:14 p.m.