Triple
T10908376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mcDJ Recording |
E257628
|
entity |
| Predicate | associatedRoleOfFounder |
P7059
|
FINISHED |
| Object | rapper |
—
|
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: rapper | Statement: [mcDJ Recording, associatedRoleOfFounder, rapper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedRoleOfFounder Context triple: [mcDJ Recording, associatedRoleOfFounder, rapper]
-
A.
hasCoFounderRoleOf
Indicates that one entity holds the role or position of co-founder in relation to another entity, such as an organization or venture.
-
B.
founderRole
chosen
Indicates that an entity serves as a founder in relation to another entity, specifying the role or capacity in which they established it.
-
C.
hasCoFounderRole
Indicates that an entity holds or is assigned the role of co-founder in relation to another entity (such as an organization or project).
-
D.
associatedInstitutionFounder
Indicates that an entity is the founder or co-founder of a particular institution with which they are associated.
-
E.
coFounderOfFounder
Indicates that one entity is a co-founder of another entity who is themselves a founder of something else.
- 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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7706824d08190ba894d144cc6b3ba |
completed | April 9, 2026, 9:24 a.m. |
| PD | Predicate disambiguation | batch_69d70d3d69e08190bb369e9a7927142c |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:22 p.m.