Triple
T20124743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biscuits for Breakfast |
E490719
|
entity |
| Predicate | hasRecordingArtistOccupation |
P107299
|
FINISHED |
| Object | singer-songwriter |
—
|
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: singer-songwriter | Statement: [Biscuits for Breakfast, hasRecordingArtistOccupation, singer-songwriter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecordingArtistOccupation Context triple: [Biscuits for Breakfast, hasRecordingArtistOccupation, singer-songwriter]
-
A.
hasMusicalArtistOccupation
Indicates that an entity has an occupation or professional role as a musical artist.
-
B.
artistOccupation
Indicates the professional role or job that an artist holds or performs.
-
C.
hasMainPerformerOccupation
Indicates that an entity’s primary or main performer is associated with a specified occupation or professional role.
-
D.
hasArtistRole
Indicates that an entity serves in the capacity or role of an artist in relation to another entity or context.
-
E.
featuresArtistAsRecordingArtist
chosen
Indicates that an item (such as a recording or release) includes a particular artist in the role of the recording artist.
- 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_69da62651a0c8190a3e05e95e056a66b |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e667412b888190b43f7dd1ccdbad01 |
completed | April 20, 2026, 5:49 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:31 p.m.