Triple
T36878098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Way Mirror |
E911395
|
entity |
| Predicate | hasPrimaryMusicalRole |
P24740
|
FINISHED |
| Object | singer-songwriter |
—
|
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: singer-songwriter | Statement: [Three Way Mirror, hasPrimaryMusicalRole, singer-songwriter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryMusicalRole Context triple: [Three Way Mirror, hasPrimaryMusicalRole, singer-songwriter]
-
A.
hasPrimaryMusician
Indicates that an entity has a specific musician designated as its main or principal performer.
-
B.
occupationInMusical
Indicates that an entity holds a specific occupation or role within the context of a musical work or production.
-
C.
hasMusicalRoleOfCreator
Indicates that an entity serves as the originating creator (e.g., composer, songwriter) responsible for bringing a musical work into existence.
-
D.
musicalRole
chosen
Indicates the specific function or part an entity performs within a musical context, such as in a performance, composition, or ensemble.
-
E.
hasMusicSpecialism
Indicates that an entity has a particular area of specialization or focus within the field of music.
- 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_69f76e82339881909607a65c0503d941 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.