Triple
T33505254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heat (music contributor) |
E858094
|
entity |
| Predicate | primaryRoleOfCreator |
P13180
|
FINISHED |
| Object | lead guitarist |
—
|
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: lead guitarist | Statement: [Heat (music contributor), primaryRoleOfCreator, lead guitarist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRoleOfCreator Context triple: [Heat (music contributor), primaryRoleOfCreator, lead guitarist]
-
A.
creatorOccupation
Indicates the professional role or job that the creator of an entity holds or held.
-
B.
relatedWorkCreatorOccupation
Indicates that the occupation specified is the professional role or job held by the creator of a related work.
-
C.
primaryRoleFor
Indicates that one entity serves as the main or most important role or function for another entity.
-
D.
fieldOfWorkOfCreator
Indicates the professional or thematic field in which a creator primarily works or produces their creations.
-
E.
creatorType
chosen
Indicates the role or category of a creator in relation to the creation of something (e.g., author, artist, director).
- 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_69f3497660508190a541826a81f7e9ab |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:38 a.m.