Triple
T4554061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deric Angelettie |
E120439
|
entity |
| Predicate | notableAliasRole |
P27764
|
FINISHED |
| Object | comedic skits as The Mad 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: comedic skits as The Mad Rapper | Statement: [Deric Angelettie, notableAliasRole, comedic skits as The Mad Rapper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAliasRole Context triple: [Deric Angelettie, notableAliasRole, comedic skits as The Mad Rapper]
-
A.
notableHolderRole
Indicates that an entity is recognized for holding a particular role, office, or position in a notable or distinguished capacity.
-
B.
hasNotableRoleIn
chosen
Indicates that an entity holds a significant or noteworthy role or function within another entity, event, work, or context.
-
C.
namedPersonRole
Indicates that a person is identified by name as holding a specific role or position in a given context.
-
D.
notationRole
Indicates a role or function that an entity plays specifically within a system of notation or symbolic representation.
-
E.
refersToRole
Indicates that one entity designates, mentions, or points to another entity specifically in its capacity as a role or position.
- 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_69bd4636f1648190a701445c2fcd9c17 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd58127ed08190a04962a43afb888b |
completed | March 20, 2026, 2:22 p.m. |
| PD | Predicate disambiguation | batch_69bd5223423c81908317351b58cff5f5 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:09 p.m.