Triple
T16500663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yesterdays |
E400789
|
entity |
| Predicate | trackNumberOnUseYourIllusionII |
P7270
|
FINISHED |
| Object | 11 |
—
|
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: 11 | Statement: [Yesterdays, trackNumberOnUseYourIllusionII, 11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackNumberOnUseYourIllusionII Context triple: [Yesterdays, trackNumberOnUseYourIllusionII, 11]
-
A.
trackNumberOnAlbum
chosen
Indicates the specific position or sequence number that a track occupies on an album.
-
B.
Pillar IIInstrument
Indicates a relationship where an entity serves as the specific instrument, mechanism, or tool used to implement or operationalize a second “Pillar II” entity.
-
C.
trackUsed
Indicates that a particular track (such as a route, path, or media track) has been utilized or selected in a given context.
-
D.
isTrackNumberUnknown
Indicates that the track number associated with an item or entity is not known or has not been specified.
-
E.
isDoubleAlbumTrack
Indicates that a track belongs to an album that was released as a double album (i.e., spanning two discs or equivalent units).
- 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e4ddc88819081fedb726add3e96 |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.