Triple
T24054483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Larry Lovestein |
E595756
|
entity |
| Predicate | alternatePersonaOf |
P118062
|
FINISHED |
| Object | Mac Miller |
—
|
NE NERFINISHED |
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: Mac Miller | Statement: [Larry Lovestein, alternatePersonaOf, Mac Miller]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alternatePersonaOf Context triple: [Larry Lovestein, alternatePersonaOf, Mac Miller]
-
A.
characterRoleSwap
Indicates a relationship where two characters exchange or assume each other’s narrative roles or functions within a story or scenario.
-
B.
ultimatePersona
Indicates that one entity represents the final, most complete, or most authoritative persona or identity of another entity.
-
C.
roleOfCharacter
Indicates that one entity serves as the narrative or functional role played by a character within a story, scenario, or context.
-
D.
roleInCharacterBackstory
Indicates that one entity plays a specific role or part in shaping another entity’s character backstory or personal history.
-
E.
fictionalPersonaOf
chosen
Indicates that one entity is a fictional or narrative persona, alter ego, or character representation of another (typically real or primary) 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_69e288c184b081909f1f1751fb8e299a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d9d551288190a2b3b6c8c4f3c1b5 |
completed | April 29, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:21 p.m.