Triple
T29870808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ganke Lee |
E758589
|
entity |
| Predicate | supportsAsSuperhero |
P131662
|
FINISHED |
| Object | Miles Morales |
E378747
|
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: Miles Morales | Statement: [Ganke Lee, supportsAsSuperhero, Miles Morales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAsSuperhero Context triple: [Ganke Lee, supportsAsSuperhero, Miles Morales]
-
A.
hasSuperheroMantle
Indicates that one entity holds or has assumed the superhero identity, title, or role associated with another entity.
-
B.
superheroStatus
Indicates that an entity possesses the qualities, role, or designation of being a superhero, such as having heroic abilities, identity, or status.
-
C.
associatedWithSuperhero
chosen
Indicates that one entity has a notable connection, link, or involvement with a superhero entity.
-
D.
hasSuperpower
Indicates that one entity possesses a special or extraordinary power or ability beyond normal human capabilities.
-
E.
usesSuperheroIdentity
Indicates that an entity adopts or operates under a superhero persona or alias, rather than their ordinary identity.
- 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_69f2245d0d7081909e37ee328542bcd7 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a277bf54fdc8190b407b6fb5dd76bcb |
completed | June 9, 2026, 2:35 a.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 5:53 p.m.