Triple
T31317163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USBMR1400128 |
E798626
|
entity |
| Predicate | associatedWithPerformerRole |
P86543
|
FINISHED |
| Object | lead artist |
—
|
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 artist | Statement: [USBMR1400128, associatedWithPerformerRole, lead artist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithPerformerRole Context triple: [USBMR1400128, associatedWithPerformerRole, lead artist]
-
A.
associatedWithPerformer
Indicates a relationship in which something (such as a work, event, or role) is connected or linked to a specific performer.
-
B.
associatedPerformerPersona
chosen
Indicates a relationship where a performer is linked to a specific persona or role identity they adopt in their performances.
-
C.
performerRelationshipContext
Indicates the contextual nature or circumstances of the relationship between a performer and another entity (such as an event, work, or role).
-
D.
associatedWithArtistType
Indicates that an entity has a connection or linkage to a particular category or type of artist.
-
E.
associatedWithCharacterRole
Indicates that one entity has a connection or linkage to a specific character role played or held by another 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_69f224e1932c81908fef14f7b03a10b7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:15 p.m.