Triple
T18049120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Can't Keep a Good Man Down |
E431879
|
entity |
| Predicate | isBside |
P15273
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Can't Keep a Good Man Down, isBside, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBside Context triple: [Can't Keep a Good Man Down, isBside, true]
-
A.
hasBside
chosen
Indicates that one item serves as the B-side counterpart or secondary track associated with another primary item, typically in a recording or media release.
-
B.
onAlbumSide
Indicates that a particular track or song appears on a specified side (e.g., Side A or Side B) of an album.
-
C.
A-sideWith
Indicates that one entity is aligned or positioned on the same side as another entity.
-
D.
hasNotableA-Side
Indicates that an item (typically a single or record) is associated with a specific notable A-side track.
-
E.
isDoubleAAsideWith
Indicates that two entities are paired together as a double A-side, typically sharing equal prominence in a joint release (such as two lead tracks on the same single).
- 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_69d8b906482481908183315b9ecf9994 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4bff4a6e08190a5ca8d191aa7f0ae |
completed | April 19, 2026, 11:43 a.m. |
| PD | Predicate disambiguation | batch_69e3f908da508190a088aa837ea5b7af |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:25 a.m.