Triple
T23945999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clavicordium |
E602914
|
entity |
| Predicate | volumeComparedToPiano |
P154453
|
FINISHED |
| Object | much softer |
—
|
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: much softer | Statement: [Clavicordium, volumeComparedToPiano, much softer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: volumeComparedToPiano Context triple: [Clavicordium, volumeComparedToPiano, much softer]
-
A.
instrumentsComparableTo
Indicates that two instruments are similar enough in characteristics or function to be meaningfully compared.
-
B.
hasPianoStyle
Indicates that one entity possesses, is associated with, or is characterized by a particular style or manner of piano playing.
-
C.
hasPianos
Indicates that one entity possesses, contains, or includes one or more pianos in relation to another entity.
-
D.
parentInstrument
Indicates that one instrument serves as the broader, containing, or originating instrument from which another, more specific or derived instrument is related.
-
E.
isPianoDriven
Indicates that something is primarily led, dominated, or characterized by the piano in its musical arrangement or performance.
- F. None of above. chosen
Provenance (4 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_69e2953e4924819093f1c24c03476b42 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d02dd0cc8190b32eb86bdfe0bf9a |
completed | April 29, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 9:13 p.m.