Triple
T32761486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mekaal Hasan |
E837767
|
entity |
| Predicate | isBandleaderOf |
P56624
|
FINISHED |
| Object | Mekaal Hasan 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: Mekaal Hasan Band | Statement: [Mekaal Hasan, isBandleaderOf, Mekaal Hasan Band]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBandleaderOf Context triple: [Mekaal Hasan, isBandleaderOf, Mekaal Hasan Band]
-
A.
houseBandLeader
Indicates that one entity serves as the leader of a house band associated with another entity (such as a venue, show, or organization).
-
B.
bandLeader
chosen
Indicates that one entity serves as the leader or primary directing figure of a musical band that includes the other entity.
-
C.
isFrontmanOf
Indicates that a person serves as the lead singer or primary representative performer of a band or musical group.
-
D.
hasBandMember
Indicates that a musical group includes a specific individual as one of its members.
-
E.
workedAsSessionMusicianFor
Indicates that one entity performed as a session musician providing musical services or recordings for another entity, typically an artist, band, or production.
- 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_69f34939857c8190aa9970c51feec1eb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce6d659881909ddcec1d2966e020 |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:13 a.m.