Triple
T37928584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lockout |
E946154
|
entity |
| Predicate | hasWeaponSpawn |
P191418
|
FINISHED |
| Object | Battle 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: Battle Rifle | Statement: [Lockout, hasWeaponSpawn, Battle Rifle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWeaponSpawn Context triple: [Lockout, hasWeaponSpawn, Battle Rifle]
-
A.
hasGrenadeSpawn
Indicates that a location or entity serves as a spawn point where grenades can appear or be generated.
-
B.
hasWeaponBoxLocation
Indicates that an entity has a specific location associated with a weapon box.
-
C.
canSpawnWithEquipment
Indicates that an entity is able to appear or be created already equipped with items or gear.
-
D.
isStartingWeaponFor
Indicates that a weapon is the initial or default weapon assigned to or used by an entity at the start of a game, scenario, or progression.
-
E.
hasWeaponType
Indicates that an entity is associated with or equipped with a specific type or category of weapon.
- 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_69f76ef3b7248190892fb9706423be7c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
| PDg | Predicate description generation | batch_69fcdf22ab8881908b257f16522920c5 |
completed | May 7, 2026, 6:51 p.m. |
Created at: May 3, 2026, 4:20 p.m.