Triple
T6526031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clavichord |
E151303
|
entity |
| Predicate | hasSoundProductionMethod |
P3514
|
FINISHED |
| Object | Strings struck by tangents |
—
|
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: Strings struck by tangents | Statement: [Clavichord, hasSoundProductionMethod, Strings struck by tangents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSoundProductionMethod Context triple: [Clavichord, hasSoundProductionMethod, Strings struck by tangents]
-
A.
soundReproductionMethod
chosen
Indicates the method or technique used to reproduce or play back sound.
-
B.
hasProductionMethod
Indicates that one entity is produced, created, or manufactured using the method, process, or technique specified by another entity.
-
C.
hasSound
Indicates that an entity produces, emits, or is associated with a particular sound.
-
D.
hasSoundSystem
Indicates that an entity is equipped with or includes a sound system as one of its features.
-
E.
hasPartialSound
Indicates that one entity’s sound is included as a component or segment within the sound 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_69c687f522748190b3058405553cdabd |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ada77b448190b6e0e07494fb4dd3 |
completed | March 27, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69c68abbc7148190a8270d47fe10cc31 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:45 p.m.