Triple
T37911342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Phoenix Saga |
E945696
|
entity |
| Predicate | introducesAlterEgo |
P111286
|
FINISHED |
| Object | Phoenix |
—
|
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: Phoenix | Statement: [The Phoenix Saga, introducesAlterEgo, Phoenix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducesAlterEgo Context triple: [The Phoenix Saga, introducesAlterEgo, Phoenix]
-
A.
protagonistAlterEgoOf
Indicates that one entity is the alternate identity or secret persona of the main character (protagonist) in a narrative.
-
B.
hasFictionalAlterEgoOf
Indicates that one entity is the fictional alter ego, persona, or alternate identity of another entity.
-
C.
introducesSuperhero
Indicates that one entity presents or brings a superhero character into a story, context, or situation for the first time.
-
D.
introducesSuperheroIdentity
chosen
Indicates that one entity reveals or presents the superhero persona or codename of another entity (or themselves) to an audience or context.
-
E.
introducesName
Indicates that one entity presents or gives a name or designation to another 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_69f76ef20bb0819088b5b6ceecb0b8fc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff0e9c75208190a4423261f00b79b3 |
completed | May 9, 2026, 10:38 a.m. |
| PD | Predicate disambiguation | batch_69ff0e07f08481909c4ae322632a6bf0 |
completed | May 9, 2026, 10:35 a.m. |
Created at: May 3, 2026, 4:20 p.m.