Triple
T38634433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wolverines! |
E937539
|
entity |
| Predicate | hasWeaponAvailability |
P166460
|
FINISHED |
| Object | assault rifles |
—
|
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: assault rifles | Statement: [Wolverines!, hasWeaponAvailability, assault rifles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWeaponAvailability Context triple: [Wolverines!, hasWeaponAvailability, assault rifles]
-
A.
hasWeaponSpawn
Indicates that a location, object, or entity serves as a spawn point where weapons can appear or be generated.
-
B.
hasWeaponOption
chosen
Indicates that an entity has a particular weapon available as a selectable or usable option.
-
C.
hasWeaponType
Indicates that an entity is associated with or equipped with a specific type or category of weapon.
-
D.
enablesWeapon
Indicates that one entity provides the capability for another entity to use, activate, or access a weapon.
-
E.
hasWeaponForm
Indicates that one entity takes the form of, or is manifested as, a particular 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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: May 3, 2026, 4:32 p.m.