Triple
T11639163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guy Hedlund |
E276611
|
entity |
| Predicate | artistic role |
P73761
|
FINISHED |
| Object | performer |
—
|
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: performer | Statement: [Guy Hedlund, artistic role, performer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: artistic role Context triple: [Guy Hedlund, artistic role, performer]
-
A.
roleInArt
chosen
Indicates the specific function, position, or contribution an entity has within a particular artwork or artistic production.
-
B.
musicalRole
Indicates the specific function or part an entity performs within a musical context, such as in a performance, composition, or ensemble.
-
C.
roleInArtScene
Indicates that an entity holds a particular function, position, or involvement within an artistic or cultural scene.
-
D.
actorRole
Indicates that an entity participates in an event or action in a specific capacity or function (such as performer, initiator, or responsible party).
-
E.
creativeRole
Indicates that an entity holds a specific creative function or responsibility in relation to another entity, such as a work or project.
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a25e90c08190b7fb73939a2be3d7 |
completed | April 10, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dd94bdc819091fa2ed33eb31624 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.