Triple
T33244814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cervenka |
E851066
|
entity |
| Predicate | bearerRoleInBand |
P118484
|
FINISHED |
| Object | vocalist of X |
—
|
LITERAL FINISHED |
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: vocalist of X | Statement: [Cervenka, bearerRoleInBand, vocalist of X]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bearerRoleInBand Context triple: [Cervenka, bearerRoleInBand, vocalist of X]
-
A.
hasRoleInBand
chosen
Indicates that an entity holds a specific role or position within a band.
-
B.
associatedWithBandMemberPersona
Indicates a relationship where an entity is connected to or linked with the persona or role of a band member.
-
C.
contributingBandMember
Indicates that an individual is a member of a band who contributes to its music, performance, or creative output.
-
D.
musicalEnsembleRole
Indicates the specific function or position an individual holds within a musical ensemble, such as performer, conductor, or composer.
-
E.
usesBand
Indicates that one entity employs or makes use of a particular band (such as a group, frequency band, or band resource) in performing an action or fulfilling a function.
- 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_69f34962386c81909ddc3bf9e18ddeb8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 1:31 a.m.