Triple
T33193484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samantha |
E849678
|
entity |
| Predicate | hasBandleaderPerformer |
P56624
|
FINISHED |
| Object | Kenny Ball |
—
|
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: Kenny Ball | Statement: [Samantha, hasBandleaderPerformer, Kenny Ball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBandleaderPerformer Context triple: [Samantha, hasBandleaderPerformer, Kenny Ball]
-
A.
hasBandLeaderRoleOf
Indicates that one entity serves in the role of band leader for another entity (typically a band or musical group).
-
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.
houseBandLeader
Indicates that one entity serves as the leader of a house band associated with another entity (such as a venue, show, or organization).
-
D.
hasBackingMusiciansFrom
Indicates that an artist or musical act is supported or accompanied by backing musicians who originate from a specified place or group.
-
E.
hasPerformerFamily
Indicates that an entity has a family member who performs or participates as a performer in relation to that 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_69f3495e0f108190a6a7006f79f9c2c3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: May 1, 2026, 1:29 a.m.