Triple
T37928591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lockout |
E946154
|
entity |
| Predicate | hasPowerWeapon |
P6014
|
FINISHED |
| Object | Sniper 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: Sniper Rifle | Statement: [Lockout, hasPowerWeapon, Sniper Rifle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPowerWeapon Context triple: [Lockout, hasPowerWeapon, Sniper Rifle]
-
A.
hasEnergyWeapons
Indicates that an entity is equipped with or uses weapons that emit or manipulate energy (such as lasers or plasma) rather than conventional physical projectiles.
-
B.
hasPower
Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
-
C.
hasWeaponType
chosen
Indicates that an entity is associated with or equipped with a specific type or category of weapon.
-
D.
hasCannon
Indicates that one entity is equipped with, contains, or features a cannon.
-
E.
hasWeaponOption
Indicates that an entity has a particular weapon available as a selectable or usable option.
- 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_69f76ef3b7248190892fb9706423be7c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fff9b126b4819085a4cf8791d388d1 |
completed | May 10, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69fff8f913a881908d3b7e490d92631f |
completed | May 10, 2026, 3:18 a.m. |
Created at: May 3, 2026, 4:20 p.m.