Triple
T24601599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Repaid in Full: The Paid in Full Remixed |
E608838
|
entity |
| Predicate | primaryDJProducer |
P93557
|
FINISHED |
| Object | Eric 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: Eric B. | Statement: [Repaid in Full: The Paid in Full Remixed, primaryDJProducer, Eric B.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryDJProducer Context triple: [Repaid in Full: The Paid in Full Remixed, primaryDJProducer, Eric B.]
-
A.
hasMainDJOrProducer
chosen
Indicates that an entity (such as a music show, event, or recording) has a specific person or group serving as its primary DJ or producer.
-
B.
featuresDJ
Indicates that an entity includes or presents a DJ as part of its offering or composition.
-
C.
notableDJ
Indicates that the subject is recognized as a distinguished or prominent disc jockey (DJ), known for their impact or reputation in the field.
-
D.
notableDJAssociated
Indicates that there is a notable DJ who is associated with, or prominently linked to, the given entity.
-
E.
featuresDJScratching
Indicates that an audio track or performance includes DJ-style scratching as a prominent element.
- 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_69e2c4d060e08190ac9f7c49b1036e20 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6ca751c8190a040c10d701ecf3a |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:30 a.m.