Triple
T35275188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barry Bonds (Freestyle) |
E1018784
|
entity |
| Predicate | originalBeatFeaturedArtist |
P10644
|
FINISHED |
| Object | Lil Wayne |
E26484
|
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: Lil Wayne | Statement: [Barry Bonds (Freestyle), originalBeatFeaturedArtist, Lil Wayne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalBeatFeaturedArtist Context triple: [Barry Bonds (Freestyle), originalBeatFeaturedArtist, Lil Wayne]
-
A.
originalBeatPerformer
Indicates that an entity is the performer who first created or recorded the original beat or rhythmic backing for a work.
-
B.
originalBeatBy
Indicates that one entity was initially defeated, surpassed, or outperformed by another entity.
-
C.
leadSingleFeaturing
Indicates that an artist is featured on the lead single of another artist’s release.
-
D.
hasFeaturedArtist
chosen
Indicates that an entity (such as a song or track) includes another artist who appears as a featured performer.
-
E.
featuresVariousArtists
Indicates that something (typically a creative work) includes contributions from multiple distinct artists rather than a single primary artist.
- 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_69f76de5c4788190896ad598ae7d6bc6 |
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_6a380fbd397c8190bc5a058290705ee6 |
completed | June 21, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:02 p.m.