Triple
T35008118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark Logan |
E1009866
|
entity |
| Predicate | humanAlterEgoOf |
P118062
|
FINISHED |
| Object | Beast Boy |
—
|
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: Beast Boy | Statement: [Mark Logan, humanAlterEgoOf, Beast Boy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: humanAlterEgoOf Context triple: [Mark Logan, humanAlterEgoOf, Beast Boy]
-
A.
hasFictionalAlterEgoOf
Indicates that one entity is the fictional alter ego, persona, or alternate identity of another entity.
-
B.
ultimatePersona
Indicates that one entity represents the final, most complete, or most authoritative persona or identity of another entity.
-
C.
protagonistAlterEgoOf
Indicates that one entity is the alternate identity or secret persona of the main character (protagonist) in a narrative.
-
D.
characterRoleSwap
Indicates a relationship where two characters exchange or assume each other’s narrative roles or functions within a story or scenario.
-
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_69f76dcb716881909f75e4fd60ab2284 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7858aa5508190a07dde993b3356fc |
completed | May 3, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.