Triple
T4867140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Just Like a Woman |
E108997
|
entity |
| Predicate | hasCanonicalPerformerRole |
P14496
|
FINISHED |
| Object | lead vocals by Bob Dylan |
—
|
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: lead vocals by Bob Dylan | Statement: [Just Like a Woman, hasCanonicalPerformerRole, lead vocals by Bob Dylan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCanonicalPerformerRole Context triple: [Just Like a Woman, hasCanonicalPerformerRole, lead vocals by Bob Dylan]
-
A.
performerCreditedAs
Indicates that a performer is associated with a work under a specific credited name or alias.
-
B.
hasArtistRole
Indicates that an entity serves in the capacity or role of an artist in relation to another entity or context.
-
C.
hasPerformerCharacteristic
Indicates that a performer possesses a particular attribute, quality, or characteristic.
-
D.
hasMainPerformerOccupation
Indicates that an entity’s primary or main performer is associated with a specified occupation or professional role.
-
E.
hasMainRole
chosen
Indicates that an entity holds the primary or most significant role in relation to another entity or context.
- 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_69bd440d96a48190b0c87069adef2af1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6d7bb0b88190bbc24498619910fc |
completed | March 20, 2026, 3:53 p.m. |
| PD | Predicate disambiguation | batch_69bd6c27334481909ba8ac80854f7d8e |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:26 p.m.