Triple
T28353982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .577 Snider |
E718173
|
entity |
| Predicate | firingSystem |
P160790
|
FINISHED |
| Object | centerfire |
—
|
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: centerfire | Statement: [.577 Snider, firingSystem, centerfire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firingSystem Context triple: [.577 Snider, firingSystem, centerfire]
-
A.
firingSystemComponents
chosen
Indicates that certain components are part of, or belong to, a firing system used to initiate or control a firing action.
-
B.
firingControl
Indicates a relationship where one entity directs, regulates, or initiates the firing or discharge action of another entity or system.
-
C.
fireControlSystem
Indicates a relationship where a system monitors, directs, and coordinates the detection, targeting, and firing of weapons or other actuators to control the application of force or energy.
-
D.
hasFireControlSystem
Indicates that an entity is equipped with or includes a fire control system used to detect, track, and direct weapons or suppression against targets.
-
E.
firing
Indicates initiating the discharge of a weapon or explosive device toward a target.
- 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_69eff6ec27b481908c8d7b86c47893d9 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64c0d6560819087fafc08ce48e158 |
completed | May 2, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 12:48 a.m.