Triple
T23277540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurzweil PC2 |
E588762
|
entity |
| Predicate | hasSoundCategory |
P84027
|
FINISHED |
| Object | pianos |
—
|
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: pianos | Statement: [Kurzweil PC2, hasSoundCategory, pianos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSoundCategory Context triple: [Kurzweil PC2, hasSoundCategory, pianos]
-
A.
hasSound
Indicates that an entity produces, emits, or is associated with a particular sound.
-
B.
hasSoundEngineType
Indicates a relationship where an entity is associated with or characterized by a specific type of sound engine.
-
C.
containsSound
Indicates that one entity includes, embodies, or produces the sound associated with another entity.
-
D.
hasSoundSystem
Indicates that an entity is equipped with or includes a sound system as one of its features.
-
E.
soundCategory
chosen
Indicates the classification relationship where a sound is assigned to a particular category or type of sound.
- 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_69e25d16e2c08190a291de254703129e |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19578adf48190bdb129a55f86172c |
completed | April 29, 2026, 5:22 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:49 p.m.