Triple
T35764739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stevens 311D |
E1033982
|
entity |
| Predicate | triggerConfiguration |
P168702
|
FINISHED |
| Object | double triggers |
—
|
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 triggers | Statement: [Stevens 311D, triggerConfiguration, double triggers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: triggerConfiguration Context triple: [Stevens 311D, triggerConfiguration, double triggers]
-
A.
triggerCondition
Indicates the specific circumstances or state under which an associated event, action, or process is initiated or activated.
-
B.
triggerStrategy
Indicates that one entity initiates or activates a particular strategy or plan in relation to another entity or context.
-
C.
trigger
Indicates that one entity causes or initiates an event, state, or action in another entity or system.
-
D.
trapTrigger
Indicates that an entity activates or sets off a trap in the environment.
-
E.
triggerMethod
chosen
Indicates the method, mechanism, or procedure by which a particular event, action, or process is initiated or triggered.
- 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_69f76e13edd081909101629aa829c4ad |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a1c740a08190811bce8764914921 |
completed | May 3, 2026, 7:28 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.