Triple
T25199283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sniper Elite V2 |
E631081
|
entity |
| Predicate | ballisticsModel |
P158020
|
FINISHED |
| Object | accounts for bullet drop |
—
|
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: accounts for bullet drop | Statement: [Sniper Elite V2, ballisticsModel, accounts for bullet drop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ballisticsModel Context triple: [Sniper Elite V2, ballisticsModel, accounts for bullet drop]
-
A.
muzzleVelocity
Indicates the speed at which a projectile leaves the muzzle of a firearm or similar weapon at the moment it is fired.
-
B.
mainGunModel
Indicates the specific model or type designation of the primary gun or main weapon system used by an entity.
-
C.
rocketCaliber
Indicates the diameter or size classification of a rocket, typically specifying the width of its body or projectile.
-
D.
typicalMuzzleEnergy
Indicates the usual or characteristic amount of muzzle energy associated with a given weapon or ammunition type.
-
E.
gunCalibre
Indicates the relationship between a firearm and the calibre (size/diameter) of ammunition it is designed to use.
- 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_69e75a8b86c4819089eda22c843b739f |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f474b409808190b41f2edafc801130 |
completed | May 1, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_69f44d849e7c81909945438f40e35362 |
completed | May 1, 2026, 6:51 a.m. |
| PDg | Predicate description generation | batch_69f45300bd488190bb1d4160f5534ef6 |
completed | May 1, 2026, 7:15 a.m. |
Created at: April 21, 2026, 12:51 p.m.