Triple
T33914134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Superman #13 |
E869402
|
entity |
| Predicate | featuresAlterEgoOfSuperman |
P86336
|
FINISHED |
| Object | Clark Kent |
E101338
|
NE 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: Clark Kent | Statement: [Superman #13, featuresAlterEgoOfSuperman, Clark Kent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresAlterEgoOfSuperman Context triple: [Superman #13, featuresAlterEgoOfSuperman, Clark Kent]
-
A.
hasFictionalAlterEgoOf
chosen
Indicates that one entity is the fictional alter ego, persona, or alternate identity of another entity.
-
B.
daughterSuperheroAlias
Indicates that one entity is the superhero alias or identity used by the daughter of another entity.
-
C.
featuresCharacterWithSuperpowers
Indicates that the subject includes or portrays a character who possesses superhuman abilities or powers.
-
D.
fieldOfExpertiseOfAlterEgo
Indicates the specific area of knowledge or professional specialization associated with an entity’s alter ego.
-
E.
protagonistAlterEgoOf
Indicates that one entity is the alternate identity or secret persona of the main character (protagonist) in a narrative.
- F. None of above.
Provenance (4 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_69f3499869bc8190b6c33a81686af226 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a023f290e3081909a465d6cfb79518a |
completed | May 11, 2026, 8:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3689cd4dfc81908f1cc9aafc6d6d8b |
completed | June 20, 2026, 12:38 p.m. |
| PD | Predicate disambiguation | batch_6a0238d1436c8190ab0251030b01902e |
completed | May 11, 2026, 8:15 p.m. |
Created at: May 1, 2026, 1:48 a.m.