Triple
T27816401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Style |
E702682
|
entity |
| Predicate | hasOfficialAudioUpload |
P169270
|
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: [Style, hasOfficialAudioUpload, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfficialAudioUpload Context triple: [Style, hasOfficialAudioUpload, true]
-
A.
hasOnlineAudio
Indicates that an entity is associated with audio content that is available or accessible online.
-
B.
hasOfficialVideo
Indicates that an entity is associated with an officially released video version or recording.
-
C.
hasAudioFeature
Indicates that one entity possesses or is associated with a specific audio-related characteristic or property.
-
D.
hasAcousticVersionBy
Indicates that one entity is an acoustic version of another, created or performed by a specified agent.
-
E.
hasAudioReleases
Indicates that an entity has associated audio-format releases (such as recordings, tracks, or audio editions) that have been published or made available.
- 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_69ef840a16748190926719ab96120bae |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f67d691a948190afa7fb19ae7d4ac5 |
completed | May 2, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67c9ec1708190b26ccf402ed7b106 |
completed | May 2, 2026, 10:37 p.m. |
Created at: April 27, 2026, 5:45 p.m.