Triple
T9333212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Worthington direct-acting steam pump |
E224576
|
entity |
| Predicate | hasActuation |
P33529
|
FINISHED |
| Object | direct-acting |
—
|
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: direct-acting | Statement: [Worthington direct-acting steam pump, hasActuation, direct-acting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasActuation Context triple: [Worthington direct-acting steam pump, hasActuation, direct-acting]
-
A.
hasActuatorType
chosen
Indicates that an entity is equipped with or uses a specific type or category of actuator.
-
B.
hasAct
Indicates that an entity performs, participates in, or is associated with a specific act or action.
-
C.
isCapableOf
Indicates that an entity has the ability or capacity to perform a particular action or function.
-
D.
sensingAction
Indicates an action in which an entity perceives, detects, or measures some property, signal, or condition of another entity or its environment.
-
E.
activationMechanism
Indicates the process or method by which one entity initiates, triggers, or enables the activity or functioning of another entity.
- 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_69ca84286fcc81909f6e7fd7a7e862a2 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd37ecfd9481908b54e3d4187fb0ce |
completed | April 1, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69cc7a643924819097f01144734901cf |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:39 p.m.