Triple
T13595300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | clavinet |
E324800
|
entity |
| Predicate | hasDampingSystem |
P49705
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [clavinet, hasDampingSystem, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDampingSystem Context triple: [clavinet, hasDampingSystem, yes]
-
A.
hasTunedMassDamper
Indicates that an entity is equipped with or incorporates a tuned mass damper as part of its structure or system.
-
B.
dampingType
chosen
Indicates the specific kind or method of damping applied in a system or interaction between entities.
-
C.
tunedMassDamperWeight_tonnes
Indicates the weight, measured in metric tonnes, of the tuned mass damper used in a structure or system.
-
D.
suspensionType
Indicates the specific kind or configuration of suspension system associated with an entity (e.g., a vehicle or structure).
-
E.
hasDynamics
Indicates that one entity exhibits or is characterized by specific dynamic behavior, changes, or variations over time in relation to another entity or context.
- 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb057f1c881909a3bb77c659a724a |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae18eaf48190809e8b365856cde9 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:49 p.m.