Triple
T305956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | It’s Over (feat. Kanye West) |
E6300
|
entity |
| Predicate | performerRole |
P9616
|
FINISHED |
| Object | John Legend – lead vocals |
—
|
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: John Legend – lead vocals | Statement: [It’s Over (feat. Kanye West), performerRole, John Legend – lead vocals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performerRole Context triple: [It’s Over (feat. Kanye West), performerRole, John Legend – lead vocals]
-
A.
playedRoleIn
Indicates that an entity performed or assumed a specific role or character within a particular event, production, or context.
-
B.
playedBy
chosen
Indicates that a role, character, or performance is portrayed or executed by a specific person or agent.
-
C.
performedBy
Indicates that an action, task, or event is carried out or executed by a specified agent or entity.
-
D.
playedKeyRoleIn
Indicates that an entity had a major, influential, or decisive impact on the occurrence, outcome, or success of another entity or event.
-
E.
portrayedBy
Indicates that one entity serves as the actor or performer who represents or plays the role of another entity in a work or medium.
- 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_69a2e79230508190b912ecb555aae17e |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea2fba548190a5aeb1597dca96bd |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e93db11881909b07ba5e76d91feb |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.