Triple
T20925056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tired Eyes |
E515317
|
entity |
| Predicate | hasStudioAlbumTrackType |
P62508
|
FINISHED |
| Object | 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: album track | Statement: [Tired Eyes, hasStudioAlbumTrackType, album track]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStudioAlbumTrackType Context triple: [Tired Eyes, hasStudioAlbumTrackType, album track]
-
A.
hasStudioAlbumContext
Indicates that there is a contextual relationship between an entity and a specific studio album, such as information, metadata, or circumstances associated with that album.
-
B.
hasStudioAlbum
Indicates that an entity (typically an artist) is associated with or has released a particular studio album.
-
C.
hasStudioAlbumSequence
Indicates the ordered sequence in which a subject’s studio albums are released or arranged relative to one another.
-
D.
isOnOnlyStudioAlbumOfArtist
Indicates that something (typically a song or track) appears exclusively on the only studio album ever released by a given artist.
-
E.
trackOnStudioAlbum
chosen
Indicates that a musical track appears on or is included in a particular studio 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_69e0b4fb431c8190b9d40e6a72f0cc87 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6f651278481909e7194f892703828 |
completed | April 21, 2026, 4 a.m. |
| PD | Predicate disambiguation | batch_69e5c9af1fe08190953366a466950140 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:49 p.m.