Triple
T36960466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heavy Cannon |
E914293
|
entity |
| Predicate | replacesWeaponRoleOf |
P191951
|
FINISHED |
| Object | Heavy Assault Rifle |
—
|
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: Heavy Assault Rifle | Statement: [Heavy Cannon, replacesWeaponRoleOf, Heavy Assault Rifle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacesWeaponRoleOf Context triple: [Heavy Cannon, replacesWeaponRoleOf, Heavy Assault Rifle]
-
A.
refersToArmamentRole
Indicates that one entity specifies or denotes the armament-related role or function associated with another entity.
-
B.
formerWeapon
Indicates that an entity once functioned as a weapon but no longer serves in that role.
-
C.
warheadReallocation
Indicates the reassignment or redistribution of warheads from one deployment, location, or platform to another.
-
D.
weaponSystemAssociatedWith
Indicates that one entity is functionally or organizationally connected to a particular weapon system, such as by using, supporting, or being part of that system.
-
E.
weaponUpgradesFrom
chosen
Indicates that one weapon is an upgraded or improved version derived from another weapon.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe744faca881908e11e90e0a35653f |
completed | May 8, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69fe734cbf7081909a552c5cf3b5ea59 |
completed | May 8, 2026, 11:35 p.m. |
Created at: May 3, 2026, 4:13 p.m.