Triple
T13891276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dom Kennedy |
E333974
|
entity |
| Predicate | hasStrongFollowing |
P74550
|
FINISHED |
| Object | underground hip hop audience |
—
|
LITERAL 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: underground hip hop audience | Statement: [Dom Kennedy, hasStrongFollowing, underground hip hop audience]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStrongFollowing Context triple: [Dom Kennedy, hasStrongFollowing, underground hip hop audience]
-
A.
hasMajorFollowingAmong
chosen
Indicates that the subject is widely popular or influential within the specified group or audience.
-
B.
hasStrongTiesTo
Indicates a close, influential, and enduring relationship or connection exists between the referenced entities.
-
C.
hasFollowers
Indicates that an entity is followed or subscribed to by one or more other entities.
-
D.
followedIn
Indicates that one entity began following or subscribing to another entity, typically in a social or sequential context.
-
E.
followsApproximately
Indicates that one entity follows another in sequence or order, but with some allowable deviation or inexactness in timing, position, or pattern.
- 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_69d81c5dd2d48190b7a5fc1e009de936 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de23a3a24881908d81d634622fbbcc |
completed | April 14, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69dd464b1ab48190ae50bfc902bf6ef7 |
completed | April 13, 2026, 7:38 p.m. |
Created at: April 9, 2026, 10:15 p.m.