Triple
T35265872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Controlla |
E1018510
|
entity |
| Predicate | hasStreamingAvailabilityOn |
P80625
|
FINISHED |
| Object | Spotify |
—
|
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: Spotify | Statement: [Controlla, hasStreamingAvailabilityOn, Spotify]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStreamingAvailabilityOn Context triple: [Controlla, hasStreamingAvailabilityOn, Spotify]
-
A.
hasStreamingAvailability
chosen
Indicates that a media item is available to be streamed through a particular streaming service or platform.
-
B.
hasStreamingEligibility
Indicates that an entity is qualified or permitted to be made available via a streaming service or platform.
-
C.
hasStreamingRelease
Indicates that an entity has been released or made available through a streaming platform or service.
-
D.
streamingReleaseDate
Indicates the date on which a work (such as a film, show, or album) becomes available to the public via a streaming platform.
-
E.
hasStreaming
Indicates that an entity provides or supports streaming access to another entity (such as media, data, or content).
- 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_69f76de4be5c8190a51705c07612cac8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffe01c9d3c819084c256bb3c81c0dc |
completed | May 10, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69ffdfcc78b08190aa4493f13d62a531 |
completed | May 10, 2026, 1:30 a.m. |
Created at: May 3, 2026, 4:02 p.m.