Triple
T28961550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Pared |
E731910
|
entity |
| Predicate | hasOfficialAudio |
P126286
|
FINISHED |
| Object | available on streaming platforms |
—
|
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: available on streaming platforms | Statement: [La Pared, hasOfficialAudio, available on streaming platforms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfficialAudio Context triple: [La Pared, hasOfficialAudio, available on streaming platforms]
-
A.
hasOfficialAudioUpload
Indicates that an official audio version of the content has been uploaded or made available, typically by an authorized or original source.
-
B.
hasOnlineAudio
chosen
Indicates that an entity is associated with audio content that is available or accessible online.
-
C.
hasAudioFeature
Indicates that one entity possesses or is associated with a specific audio-related characteristic or property.
-
D.
hasOfficialVideo
Indicates that an entity is associated with an officially released video version or recording.
-
E.
hasAcousticVersionBy
Indicates that one entity is an acoustic version of another, created or performed by a specified agent.
- 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_69f043ee242c8190b063248b417c5a69 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 28, 2026, 8:50 a.m.