Triple
T34005057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virtual Diva |
E871935
|
entity |
| Predicate | hasFuturisticSound |
P68354
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Virtual Diva, hasFuturisticSound, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFuturisticSound Context triple: [Virtual Diva, hasFuturisticSound, true]
-
A.
hasSound
Indicates that an entity produces, emits, or is associated with a particular sound.
-
B.
hasSpaceThemedSound
chosen
Indicates that something features or uses audio whose style, effects, or ambience evoke a space or sci‑fi theme.
-
C.
hasExperimentalSound
Indicates that something possesses or exhibits an unconventional, innovative, or avant-garde sound quality or style.
-
D.
hasSoundDesignStyle
Indicates a relationship where an entity is characterized by or associated with a particular style or approach to sound design.
-
E.
hasSoundSystem
Indicates that an entity is equipped with or includes a sound system as one of its features.
- 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_69f349a08848819084b348d64c1879c3 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:50 a.m.