Triple
T37151738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vibe |
E920378
|
entity |
| Predicate | hasNotableCoverSubjects |
P135849
|
FINISHED |
| Object | Tupac Shakur |
E27310
|
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: Tupac Shakur | Statement: [Vibe, hasNotableCoverSubjects, Tupac Shakur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableCoverSubjects Context triple: [Vibe, hasNotableCoverSubjects, Tupac Shakur]
-
A.
hasNotableSubject
Indicates that an entity is associated with a subject that is particularly significant, prominent, or noteworthy in relation to it.
-
B.
hasNotableCoverArtist
Indicates that an entity has a cover (e.g., of a book, album, or publication) created by a cover artist who is considered notable.
-
C.
notableCover
Indicates that one entity is a particularly well-known or significant cover version or adaptation of another entity.
-
D.
hasNotableCoverOrInterpolation
Indicates that a work has a notable cover version or interpolation created by another artist.
-
E.
hasNotableIllustrationsOf
chosen
Indicates that something contains or features particularly significant or noteworthy illustrations depicting another entity or subject.
- 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_69f76e9f87c08190b4c8f7fafbd8345a |
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_6a402bb0bfd48190a931193da162e3f5 |
completed | June 27, 2026, 7:59 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:15 p.m.