Triple
T23831171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurzweil Artis |
E589514
|
entity |
| Predicate | hasSoundEngine |
P153777
|
FINISHED |
| Object | Kurzweil sound engine |
—
|
NE NERFINISHED |
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: Kurzweil sound engine | Statement: [Kurzweil Artis, hasSoundEngine, Kurzweil sound engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSoundEngine Context triple: [Kurzweil Artis, hasSoundEngine, Kurzweil sound engine]
-
A.
hasSoundEngineType
Indicates a relationship where an entity is associated with or characterized by a specific type of sound engine.
-
B.
hasSound
Indicates that an entity produces, emits, or is associated with a particular sound.
-
C.
hasSoundSystem
Indicates that an entity is equipped with or includes a sound system as one of its features.
-
D.
hasInitialSound
Indicates that one entity begins with the same initial sound (phoneme or onset) as another entity or specified sound.
-
E.
hasExperimentalSound
Indicates that something possesses or exhibits an unconventional, innovative, or avant-garde sound quality or style.
- 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_69e25d1922d481909cab567c06a802ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7f5de508190bd6bb6d89b8952d5 |
completed | April 29, 2026, 8:57 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
| PDg | Predicate description generation | batch_69f158b0e320819090b947ee7eb14116 |
completed | April 29, 2026, 1:02 a.m. |
Created at: April 17, 2026, 8:04 p.m.