Triple
T29309130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jacquire King |
E743181
|
entity |
| Predicate | notableAlbumMixed |
P204159
|
FINISHED |
| Object | Little Broken Hearts |
E386087
|
NE 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: Little Broken Hearts | Statement: [Jacquire King, notableAlbumMixed, Little Broken Hearts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAlbumMixed Context triple: [Jacquire King, notableAlbumMixed, Little Broken Hearts]
-
A.
notableAlbumContribution
Indicates that an entity made a significant creative or performance contribution to a particular music album.
-
B.
mixedAlbumFor
Indicates that one entity has compiled or produced a mixed album specifically for another entity.
-
C.
notableAlbumEngineered
chosen
Indicates that a person served as the audio engineer for a notable album.
-
D.
notableMixtapeOrEP
Indicates that the subject is notably associated with a specific mixtape or EP, such as by creating, releasing, or being prominently featured on it.
-
E.
isOnGenreBlendingAlbum
Indicates that something (typically a song or track) appears on an album characterized by blending or combining multiple musical genres.
- F. None of above.
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_69f09123ed9881909f351f7541933f5e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_6a033ed9322c8190be994a8d99761caa |
completed | May 12, 2026, 2:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a25a8657c908190a1ac9731f222e776 |
completed | June 7, 2026, 5:20 p.m. |
| PD | Predicate disambiguation | batch_6a033df2b254819082a672859e5168e6 |
completed | May 12, 2026, 2:49 p.m. |
Created at: April 28, 2026, 1:15 p.m.