Triple
T35214226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metal Guru |
E1016775
|
entity |
| Predicate | featuresDistinctiveVocalStyle |
P203326
|
FINISHED |
| Object | Marc Bolan |
E583164
|
NE 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: Marc Bolan | Statement: [Metal Guru, featuresDistinctiveVocalStyle, Marc Bolan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresDistinctiveVocalStyle Context triple: [Metal Guru, featuresDistinctiveVocalStyle, Marc Bolan]
-
A.
featuresVocalStyleOf
chosen
Indicates that one entity exhibits or incorporates the distinctive vocal style or vocal characteristics associated with another entity.
-
B.
hasDistinctiveVoice
Indicates that an entity possesses a voice that is notably unique or easily distinguishable from others.
-
C.
introducedVocalStyleOf
Indicates that one entity initiated or brought into use the vocal style characteristic of another entity.
-
D.
hasVocalStyleComparedTo
Indicates a comparison between entities based on the similarity or resemblance of their vocal style.
-
E.
artisticVocalStyle
Indicates a relationship where an entity’s vocal performance is characterized by a particular artistic style or expressive manner of singing or speaking.
- F. None of above.
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_69f76ddf549c8190869d0af076fd2c28 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a390d29cce08190946719f04298df2f |
completed | June 22, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:02 p.m.