Triple
T24098262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Me and My Girlfriend |
E596986
|
entity |
| Predicate | hasNotableCoverOrInterpolation |
P155064
|
FINISHED |
| Object | 03 Bonnie & Clyde |
—
|
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: 03 Bonnie & Clyde | Statement: [Me and My Girlfriend, hasNotableCoverOrInterpolation, 03 Bonnie & Clyde]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableCoverOrInterpolation Context triple: [Me and My Girlfriend, hasNotableCoverOrInterpolation, 03 Bonnie & Clyde]
-
A.
hasNotableCoverArtist
Indicates that an entity has a cover (e.g., of a book, album, or publication) created by a cover artist who is considered notable.
-
B.
hasCoverFeature
Indicates that one entity serves as a prominent or featured element on the cover of another entity (such as a publication, product, or media item).
-
C.
hasCoverType
Indicates that one entity possesses or is associated with a specific type or category of cover.
-
D.
containsCoverOf
Indicates that one entity includes within it a cover or covering representation of another entity.
-
E.
iconCoveredBy
Indicates that one icon is visually overlapped or obscured by another icon in the interface.
- F. None of above. chosen
Provenance (4 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_69e288c548048190a5c1018da1166a21 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dd2717d881909d1d0b270b758643 |
completed | April 29, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
| PDg | Predicate description generation | batch_69f17b58012c81909106b332db399023 |
completed | April 29, 2026, 3:30 a.m. |
Created at: April 17, 2026, 10:59 p.m.