Triple
T10677399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La strada (film score) |
E251653
|
entity |
| Predicate | hasReleases |
P22087
|
FINISHED |
| Object | various soundtrack album editions |
—
|
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: various soundtrack album editions | Statement: [La strada (film score), hasReleases, various soundtrack album editions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReleases Context triple: [La strada (film score), hasReleases, various soundtrack album editions]
-
A.
hasRelease
chosen
Indicates that an entity (such as a product, work, or version) has a specific release instance or event associated with it.
-
B.
hasAlbumRelease
Indicates that an entity (typically an artist or band) has released a specific music album.
-
C.
hasLiveSingleRelease
Indicates that an entity has released a live recording of a single as an official release.
-
D.
hasRadioRelease
Indicates that an entity was released or made available specifically for radio broadcast.
-
E.
releases
Indicates that one entity causes something to be set free, emitted, or made available from its control or containment.
- 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_69d6aa5b0d2881909584b20efc5877f0 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fb9563908190a69cf4bd2c24fd2f |
completed | April 9, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8a93208190a573061387e2aebb |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:09 p.m.