Triple
T29434794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aleka's Attic |
E746538
|
entity |
| Predicate | associatedWithOccupationOfFrontman |
P207149
|
FINISHED |
| Object | actor |
—
|
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: actor | Statement: [Aleka's Attic, associatedWithOccupationOfFrontman, actor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithOccupationOfFrontman Context triple: [Aleka's Attic, associatedWithOccupationOfFrontman, actor]
-
A.
associatedWithBandMemberPersona
Indicates a relationship where an entity is connected to or linked with the persona or role of a band member.
-
B.
isFrontmanOf
Indicates that a person serves as the lead singer or primary representative performer of a band or musical group.
-
C.
originalBandOfFrontman
Indicates that the specified band is the first (earliest) band in which the given frontman originally served as the lead member.
-
D.
associatedBandOfMembers
Indicates a relationship where a specific band is linked to the individual members who belong to or perform in that band.
-
E.
hasFrontmanRole
Indicates that an entity holds the primary lead or frontman role within a group, band, or ensemble.
- F. None of above. chosen
Provenance (4 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_69f0a7a180e48190ae775e40047dbcb5 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 28, 2026, 3:15 p.m.