Triple
T37336402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Bronx |
E926904
|
entity |
| Predicate | notableFigureAssociatedWith |
P26467
|
FINISHED |
| Object | DJ Kool Herc |
E529331
|
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: DJ Kool Herc | Statement: [The Bronx, notableFigureAssociatedWith, DJ Kool Herc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFigureAssociatedWith Context triple: [The Bronx, notableFigureAssociatedWith, DJ Kool Herc]
-
A.
historicalFigureAssociated
chosen
Indicates that there is a notable connection or linkage between an entity and a historical figure, such as influence, collaboration, representation, or involvement in the figure’s life or legacy.
-
B.
notableCulturalFigure
Indicates that a person holds significant influence or recognition within a culture’s arts, traditions, values, or public life.
-
C.
notableHistoricalEntity
Indicates that an entity holds recognized historical significance or prominence within a historical context.
-
D.
namedPersonNotableFor
Indicates that a person is especially known or recognized for a particular work, role, achievement, or characteristic.
-
E.
notableHuman
Indicates that the subject is a human who is recognized as notable or significant in some context.
- 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_69f76eb4e8a881908bd40da28f36fc7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4063a7af1c8190ab08be824cc1adcd |
completed | June 27, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.