Triple
T37486941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All Ghillied Up |
E931556
|
entity |
| Predicate | hasSniperRifle |
P156046
|
FINISHED |
| Object | M21 |
—
|
NE NERFINISHED |
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: M21 | Statement: [All Ghillied Up, hasSniperRifle, M21]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSniperRifle Context triple: [All Ghillied Up, hasSniperRifle, M21]
-
A.
hasSniper
chosen
Indicates that an entity possesses, is equipped with, or is accompanied by a sniper (e.g., a sniper weapon or sniper specialist).
-
B.
isServiceRifleOf
Indicates that one entity is the designated service rifle used by another entity, typically a military or armed force.
-
C.
hasCannon
Indicates that one entity is equipped with, contains, or features a cannon.
-
D.
hasKillerWeapon
Indicates that a particular weapon was used by an entity to commit a killing.
-
E.
лучший снайпер
Indicates that one entity is considered the best sniper compared to others, typically in terms of accuracy, skill, or effectiveness.
- 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_69f76ec382248190b47844df596123c6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.