Triple
T23547134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swizz Beatz Productions |
E577929
|
entity |
| Predicate | primaryRoleOfFounder |
P5394
|
FINISHED |
| Object | hip hop producer |
—
|
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: hip hop producer | Statement: [Swizz Beatz Productions, primaryRoleOfFounder, hip hop producer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRoleOfFounder Context triple: [Swizz Beatz Productions, primaryRoleOfFounder, hip hop producer]
-
A.
founderRole
Indicates that an entity serves as a founder in relation to another entity, specifying the role or capacity in which they established it.
-
B.
workIncludesRoleOfFounder
Indicates that a work involves or credits an entity in the specific role of founder.
-
C.
coFounderOccupation
Indicates that the specified occupation is or was held by a person in their role as a co-founder of an organization.
-
D.
foundingRole
chosen
Indicates the specific role or capacity an entity held in the founding or establishment of another entity.
-
E.
associatedProfessionOfFounder
Indicates the professional field or occupation linked to the founder of an entity.
- 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_69e245fa93448190919cb04534560542 |
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.