Triple
T25247478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love Hurts (Incubus song) |
E632642
|
entity |
| Predicate | performerBandName |
P142463
|
FINISHED |
| Object | Incubus (American rock band) |
—
|
NE NERFINISHED |
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: Incubus (American rock band) | Statement: [Love Hurts (Incubus song), performerBandName, Incubus (American rock band)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performerBandName Context triple: [Love Hurts (Incubus song), performerBandName, Incubus (American rock band)]
-
A.
performerFullName
Indicates the complete name of the entity that performs an action or role in the described context.
-
B.
performerMemberOf
Indicates that a performer is a member of, or affiliated with, a particular group, organization, or ensemble.
-
C.
bandNameInShow
Indicates that a particular band name is used or appears within a specific show.
-
D.
byBandOrGroup
chosen
Indicates that something (such as a work, performance, or recording) is created, performed, or produced by a specific band or musical group.
-
E.
associatedBandLineup
Indicates that there is a specific band lineup (i.e., configuration of band members) that is linked or connected to the given entity.
- 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_69e75a8fdd3881909ba0b05aa5da92a7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 21, 2026, 1:10 p.m.