Triple
T24455501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unusual Heat |
E616671
|
entity |
| Predicate | previousVocalistReplaced |
P112735
|
FINISHED |
| Object | Lou Gramm |
—
|
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: Lou Gramm | Statement: [Unusual Heat, previousVocalistReplaced, Lou Gramm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousVocalistReplaced Context triple: [Unusual Heat, previousVocalistReplaced, Lou Gramm]
-
A.
previousLeadVocalistReplaced
chosen
Indicates that one person formerly served as the lead vocalist of a group and was subsequently replaced in that role by another person.
-
B.
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.
-
C.
previousDrummerReplaced
Indicates that one drummer took over the role from, and thus replaced, another drummer in a band or musical act.
-
D.
hasNewVocalist
Indicates that an entity has acquired or is associated with a different or recently joined vocalist compared to before.
-
E.
replacedDrummer
Indicates that one drummer took over the role or position previously held by another drummer.
- 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_69e2d7ef9fe08190a0613908758b4e86 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f298c5b510819099a92da4c100ded1 |
completed | April 29, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:18 a.m.