Triple
T14881626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruthless Records |
E350012
|
entity |
| Predicate | founderRoleOfEazy-E |
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: [Ruthless Records, founderRoleOfEazy-E, rapper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: founderRoleOfEazy-E Context triple: [Ruthless Records, founderRoleOfEazy-E, rapper]
-
A.
founderKnownFor
Indicates that a founder is particularly recognized or notable for a specific work, achievement, product, or contribution.
-
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.
founderAlsoKnownAs
Indicates that an individual who is a founder of something is also known by an alternative name or alias.
-
D.
wasFoundedBy
Indicates that an organization, institution, or entity came into existence through the initiating action or establishment by a specific founder or founding group.
-
E.
eponymousFounderOf
Indicates that a person is the namesake founder after whom an organization, place, or entity is named.
- 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_69d822ee4f408190b6ac3b2fa434f0df |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded5e7c0e48190af2d68a71130585c |
completed | April 15, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69de8c1a2bcc81908f914e2e2ced65eb |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:56 a.m.