Triple
T36682688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ray’s Blues |
E905728
|
entity |
| Predicate | hasNotableArtistNickname |
P25214
|
FINISHED |
| Object | The Genius |
E351718
|
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: The Genius | Statement: [Ray’s Blues, hasNotableArtistNickname, The Genius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableArtistNickname Context triple: [Ray’s Blues, hasNotableArtistNickname, The Genius]
-
A.
notableNickname
chosen
Indicates that one entity is a well-known or widely recognized nickname or moniker for another entity.
-
B.
associatedWithArtistNickname
Indicates that an entity is connected to or identified by a particular artist’s nickname or pseudonym.
-
C.
hasNicknames
Indicates that an entity is known or referred to by one or more alternative informal names.
-
D.
hasNotablePerformer
Indicates that an entity features or is associated with a performer who is particularly prominent, famous, or otherwise noteworthy.
-
E.
hasDrummerWithNickname
Indicates that an entity has a drummer who is known or referred to by a specific nickname.
- 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_69f76e7011dc819082b324f18b756a1b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3a20e1c8c08190be135ab4fc433be0 |
completed | June 23, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.