Triple
T23546600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Check on It (Remix featuring Bun B and Slim Thug) |
E577911
|
entity |
| Predicate | hasAdditionalVersesBy |
P44672
|
FINISHED |
| Object | Bun B |
—
|
NE NERFINISHED |
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: Bun B | Statement: [Check on It (Remix featuring Bun B and Slim Thug), hasAdditionalVersesBy, Bun B]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdditionalVersesBy Context triple: [Check on It (Remix featuring Bun B and Slim Thug), hasAdditionalVersesBy, Bun B]
-
A.
featuresAdditionalVersesBy
chosen
Indicates that a work includes extra or bonus verses contributed by another creator beyond the primary one.
-
B.
hasMultipleVerses
Indicates that something, typically a song, poem, or text, consists of more than one verse.
-
C.
hasVersesBy
Indicates a relationship where a work, such as a song or poem, contains verses authored or written by a specific creator.
-
D.
hasVersesIn
Indicates that one entity (typically a text, chapter, or section) contains or is composed of verses found within another entity (such as a book, collection, or scripture).
-
E.
containsVerse
Indicates that one entity (typically a text or collection) includes a specific verse as part of its content.
- 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_69e245f9d5d08190a4a20004e1784e20 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1aecb567c8190a54d2c3b63282af5 |
completed | April 29, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:11 p.m.