Triple
T27833432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Butler automation |
E703161
|
entity |
| Predicate | canTriggerOn |
P24442
|
FINISHED |
| Object | field updates |
—
|
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: field updates | Statement: [Butler automation, canTriggerOn, field updates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canTriggerOn Context triple: [Butler automation, canTriggerOn, field updates]
-
A.
hasTriggerType
chosen
Indicates that an event, condition, or mechanism is associated with a specific type or category of trigger that initiates it.
-
B.
usesTriggerSystem
Indicates that one entity operates or functions by means of a trigger-based mechanism or system provided or associated with another entity.
-
C.
canBeFiredIn
Indicates that an entity (such as a weapon or device) is capable of being discharged or operated within a specified medium, environment, or container.
-
D.
canConvoke
Indicates that one entity has the authority or ability to formally call another entity or group together for a meeting or assembly.
-
E.
triggerCondition
Indicates the specific circumstances or state under which an associated event, action, or process is initiated or activated.
- 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_69ef840b94b08190950a4f77296938b2 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 5:57 p.m.