Triple
T30467832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Steven’s Underground Garage |
E775198
|
entity |
| Predicate | hasRegularDJ |
P93557
|
FINISHED |
| Object | Steven Van Zandt |
—
|
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: Steven Van Zandt | Statement: [Little Steven’s Underground Garage, hasRegularDJ, Steven Van Zandt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegularDJ Context triple: [Little Steven’s Underground Garage, hasRegularDJ, Steven Van Zandt]
-
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.
hasStudentDJs
Indicates that an entity has DJs who are students associated with it, such as performing, working, or participating in its activities.
-
C.
hasDJPerformances
Indicates that an entity features or hosts performances by a DJ.
-
D.
featuresDJ
Indicates that an entity includes or presents a DJ as part of its offering or composition.
-
E.
notableDJ
Indicates that the subject is recognized as a distinguished or prominent disc jockey (DJ), known for their impact or reputation in the field.
- 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_69f2249622a48190b1fae2e3e4ee958a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a007899cadc8190a04edd503eaf6514 |
completed | May 10, 2026, 12:22 p.m. |
| PD | Predicate disambiguation | batch_6a0078493e088190b0c5047cbe75d304 |
completed | May 10, 2026, 12:21 p.m. |
Created at: April 29, 2026, 8:11 p.m.