Triple
T28191445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Way Past Luck |
E716326
|
entity |
| Predicate | hasTrackPositionOnAlbum |
P7270
|
FINISHED |
| Object | non-single album track |
—
|
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: non-single album track | Statement: [Way Past Luck, hasTrackPositionOnAlbum, non-single album track]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrackPositionOnAlbum Context triple: [Way Past Luck, hasTrackPositionOnAlbum, non-single album track]
-
A.
trackNumberOnAlbum
chosen
Indicates the specific position or sequence number that a track occupies on an album.
-
B.
isAlbumTrack
Indicates that a track is included as part of a specific music album.
-
C.
hasTrack
Indicates that one entity possesses, includes, or is associated with a specific track (such as a path, course, or recorded item).
-
D.
vaultTrackNumberWithinAlbum
Indicates the position or index assigned to a vault (hidden or bonus) track within the track listing of a specific album.
-
E.
isSecondAlbumTrackOf
Indicates that a musical track occupies the second position in the track listing of a specified album.
- 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_69efd6b612f48190a72012b520afbd10 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
Created at: April 27, 2026, 10:25 p.m.