Triple
T2970173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VIS 100 |
E80259
|
entity |
| Predicate | triggerMechanism |
P38751
|
FINISHED |
| Object | 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: double-action/single-action | Statement: [VIS 100, triggerMechanism, double-action/single-action]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: triggerMechanism Context triple: [VIS 100, triggerMechanism, double-action/single-action]
-
A.
activationMechanism
chosen
Indicates the process or method by which one entity initiates, triggers, or enables the activity or functioning of another entity.
-
B.
triggered
Indicates that one entity causes an event, action, or process involving another entity to start or occur.
-
C.
triggerCondition
Indicates the specific circumstances or state under which an associated event, action, or process is initiated or activated.
-
D.
transitionMechanismUsedWith
Indicates that a particular transition or change from one state to another is carried out using a specified mechanism or method.
-
E.
triggerEvent
Indicates that one entity causes or initiates the occurrence of a specific event involving another entity or the system.
- 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_69ad8b14ffe881908ffed62f9595c867 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad997282b481909d078be0e70d9930 |
completed | March 8, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69ad960e71f8819088179d11248c6ed0 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:58 p.m.