Triple
T8131322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P30 pistol |
E189857
|
entity |
| Predicate | triggerSystemOption |
P68427
|
FINISHED |
| Object | DA/SA (double-action/single-action) |
—
|
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: DA/SA (double-action/single-action) | Statement: [P30 pistol, triggerSystemOption, DA/SA (double-action/single-action)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: triggerSystemOption Context triple: [P30 pistol, triggerSystemOption, DA/SA (double-action/single-action)]
-
A.
usesTriggerSystem
chosen
Indicates that one entity operates or functions by means of a trigger-based mechanism or system provided or associated with another entity.
-
B.
triggerEvent
Indicates that one entity causes or initiates the occurrence of a specific event involving another entity or the system.
-
C.
triggerCondition
Indicates the specific circumstances or state under which an associated event, action, or process is initiated or activated.
-
D.
trigger
Indicates that one entity causes or initiates an event, state, or action in another entity or system.
-
E.
tookPlaceInSystem
Indicates that an event or process occurred within, or was hosted by, a particular system or environment.
- 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_69ca82bcb4848190a9a9d036ad768642 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4c4c2e388190b86854f8b1765e61 |
completed | March 31, 2026, 4:23 a.m. |
| PD | Predicate disambiguation | batch_69cb3696379c8190a20965e59ed8f370 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:34 p.m.