Triple
T28353962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .577 Snider |
E718173
|
entity |
| Predicate | designedForFirearm |
P184847
|
FINISHED |
| Object | Snider–Enfield rifle |
—
|
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: Snider–Enfield rifle | Statement: [.577 Snider, designedForFirearm, Snider–Enfield rifle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForFirearm Context triple: [.577 Snider, designedForFirearm, Snider–Enfield rifle]
-
A.
isGasOperated
Indicates that an entity functions or operates using gas as its primary power or energy source.
-
B.
bulletDesignation
Indicates that one entity is designated or labeled as a specific bullet point or bullet-style marker in relation to another entity.
-
C.
weaponDepicted
Indicates that a weapon is visually represented or shown in association with an entity.
-
D.
gun
Indicates that one entity uses, carries, or is associated with a gun in relation to another entity or context.
-
E.
firearmActionType
Indicates the specific type or category of action performed with or by a firearm (such as firing, loading, carrying, or modifying).
- 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_69eff6ec27b481908c8d7b86c47893d9 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f7b628b17c8190aa058c1a51852a27 |
completed | May 3, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b5cadd308190a864245a21b08f9a |
completed | May 3, 2026, 8:53 p.m. |
Created at: April 28, 2026, 12:48 a.m.