Triple
T28202911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | My Hero |
E716934
|
entity |
| Predicate | hasSuperheroElement |
P142173
|
FINISHED |
| Object | yes |
—
|
LITERAL 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: yes | Statement: [My Hero, hasSuperheroElement, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuperheroElement Context triple: [My Hero, hasSuperheroElement, yes]
-
A.
hasSuperheroMantle
Indicates that one entity holds or has assumed the superhero identity, title, or role associated with another entity.
-
B.
hasSuperpower
Indicates that one entity possesses a special or extraordinary power or ability beyond normal human capabilities.
-
C.
superheroStatus
Indicates that an entity possesses the qualities, role, or designation of being a superhero, such as having heroic abilities, identity, or status.
-
D.
hasSuperpowersTheme
chosen
Indicates that the subject involves, features, or centers around the theme of characters possessing superhuman abilities or powers.
-
E.
hasSuperheroKnowledgeLevel
Indicates the degree or extent to which an entity possesses knowledge or understanding about superheroes.
- 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_69efd6b826908190857e6e7dad74ed93 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
Created at: April 27, 2026, 10:33 p.m.