Triple
T32866882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Not Strong Enough |
E840672
|
entity |
| Predicate | alternateVocalist |
P9646
|
FINISHED |
| Object | Doug Robb |
—
|
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: Doug Robb | Statement: [Not Strong Enough, alternateVocalist, Doug Robb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alternateVocalist Context triple: [Not Strong Enough, alternateVocalist, Doug Robb]
-
A.
originallyIntendedVocalist
Indicates that a person was the first or planned singer for a musical work or performance, even if they did not ultimately perform it.
-
B.
hasNewVocalist
Indicates that an entity has acquired or is associated with a different or recently joined vocalist compared to before.
-
C.
secondaryVocalist
chosen
Indicates that an entity performs as a supporting or backup singer in a vocal performance, rather than as the primary lead vocalist.
-
D.
hasOutroVocalist
Indicates that an entity (such as a song or track) features a vocalist specifically during its outro section.
-
E.
alternateCaptain
Indicates that an entity serves as the designated secondary team leader or substitute captain for another entity (typically a sports team).
- 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_69f34942465c819099b3fb47f9044f58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: May 1, 2026, 1:17 a.m.