Triple
T16862211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Stalacpipe Organ |
E409942
|
entity |
| Predicate | actuationMethod |
P83501
|
FINISHED |
| Object | electrical actuation |
—
|
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: electrical actuation | Statement: [Great Stalacpipe Organ, actuationMethod, electrical actuation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actuationMethod Context triple: [Great Stalacpipe Organ, actuationMethod, electrical actuation]
-
A.
driveMechanism
chosen
Indicates the mechanism or component that transmits power to drive or actuate another part of a system.
-
B.
interactionMechanism
Indicates the process or means by which one entity affects, influences, or interacts with another.
-
C.
controlMethods
Indicates the methods or techniques used by one entity to direct, regulate, or influence the behavior, operation, or state of another entity.
-
D.
activationMechanism
Indicates the process or method by which one entity initiates, triggers, or enables the activity or functioning of another entity.
-
E.
mobilizationMethod
Indicates the method or process by which resources, people, or assets are organized and activated for a particular purpose or operation.
- 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b5036e6c8190a3b9e525a34da2e1 |
completed | April 18, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69e32b8cbb048190878a259cc5be960e |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.