Triple
T13203097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PR-15 Ragun |
E314288
|
entity |
| Predicate | hasTriggerMechanism |
P109035
|
FINISHED |
| Object | hammer-fired |
—
|
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: hammer-fired | Statement: [PR-15 Ragun, hasTriggerMechanism, hammer-fired]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTriggerMechanism Context triple: [PR-15 Ragun, hasTriggerMechanism, hammer-fired]
-
A.
hasMechanism
Indicates that one entity operates, functions, or produces an effect through the specified mechanism or process.
-
B.
hasSlidingMechanism
Indicates that one entity possesses or incorporates a mechanism that allows parts of it to move smoothly along a track or surface in a sliding motion.
-
C.
hasArrestingGear
Indicates that an entity is equipped with a system or mechanism used to rapidly decelerate and stop another entity, typically during landing or capture.
-
D.
launchMechanism
Indicates the mechanism or system used to initiate or propel a launch of an object or process.
-
E.
hasChamber
Indicates that one entity possesses, contains, or is associated with a distinct enclosed space or compartment (a chamber).
- 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_69d806aee7308190b70a237ba2a6e3e1 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc6bc108190b5a6a265bf6e9fd4 |
completed | April 10, 2026, 11:46 p.m. |
| PDg | Predicate description generation | batch_69d98ceeb22c8190a6be666031d9e5a4 |
completed | April 10, 2026, 11:51 p.m. |
Created at: April 9, 2026, 9:17 p.m.