Triple
T23369937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piano Trap |
E593437
|
entity |
| Predicate | hasMechanismType |
P8166
|
FINISHED |
| Object | mechanical device |
—
|
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: mechanical device | Statement: [Piano Trap, hasMechanismType, mechanical device]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMechanismType Context triple: [Piano Trap, hasMechanismType, mechanical device]
-
A.
hasMechanism
chosen
Indicates that one entity operates, functions, or produces an effect through the specified mechanism or process.
-
B.
hasMechanicalFeature
Indicates that one entity possesses, includes, or is characterized by a specific mechanical component, attribute, or functionality.
-
C.
hasMechName
Indicates that an entity is associated with a specific mechanical or machine-related name or designation.
-
D.
hasTriggerMechanism
Indicates that an entity possesses or is equipped with a specific mechanism used to initiate or activate an action or process.
-
E.
definesMechanism
Indicates that one entity specifies or explains the underlying process or mechanism by which another entity operates or occurs.
- 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_69e25d2593c88190bcdf4a716a94ccb2 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a0aff84c8190a5a6bf52adae1c9a |
completed | April 29, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:32 p.m.