Triple
T16650629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Getting Better |
E404591
|
entity |
| Predicate | chronologyPositionInAlbum |
P7270
|
FINISHED |
| Object | side one 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: side one track | Statement: [Getting Better, chronologyPositionInAlbum, side one track]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologyPositionInAlbum Context triple: [Getting Better, chronologyPositionInAlbum, side one track]
-
A.
chronologyWithinAlbum
Indicates that one track or event occurs at a specific position or order relative to others within the same album’s sequence.
-
B.
chronologicalPosition
Indicates the relative ordering of one event or entity in time with respect to another.
-
C.
trackNumberOnAlbum
chosen
Indicates the specific position or sequence number that a track occupies on an album.
-
D.
discPosition
Indicates the spatial or ordinal placement of a disc relative to a reference point or within a set or structure.
-
E.
precedesTrackOnAlbum
Indicates that one track appears immediately before another track in the ordering of tracks on the same 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_69d8838a41f08190b0c3f79c47df5078 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37bf6cfc481909b183348c407e046 |
completed | April 18, 2026, 12:41 p.m. |
| PD | Predicate disambiguation | batch_69e319b1d7f08190b5ecb4a68c636c15 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:18 a.m.