Triple
T30470227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Born to Run Tour |
E775271
|
entity |
| Predicate | includedSong |
P140686
|
FINISHED |
| Object | Born to Run |
—
|
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: Born to Run | Statement: [Born to Run Tour, includedSong, Born to Run]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedSong Context triple: [Born to Run Tour, includedSong, Born to Run]
-
A.
includesSongsFrom
Indicates that one collection, playlist, or set contains one or more songs that originate from another specified source or group.
-
B.
includesSongRecording
Indicates that one entity (such as a collection, release, or compilation) contains or features a particular song recording as part of its contents.
-
C.
isSongIn
chosen
Indicates that a particular song is contained within or belongs to a specified collection, such as an album, playlist, or soundtrack.
-
D.
trackIncluded
Indicates that a particular track is contained within, or forms part of, a larger collection, release, or grouping of tracks.
-
E.
notableSongsIncluded
Indicates that certain notable or significant songs are included as part of the referenced entity (such as an album, playlist, or collection).
- 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_69f2249622a48190b1fae2e3e4ee958a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0082989e6c819099fea0e706332e37 |
completed | May 10, 2026, 1:05 p.m. |
| PD | Predicate disambiguation | batch_6a0081ed6a1481908baf472876e28db9 |
completed | May 10, 2026, 1:02 p.m. |
Created at: April 29, 2026, 8:11 p.m.