Triple
T18527690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thunderbolt Ross |
E452760
|
entity |
| Predicate | speciesAsRedHulk |
P91503
|
FINISHED |
| Object | gamma-mutated being |
—
|
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: gamma-mutated being | Statement: [Thunderbolt Ross, speciesAsRedHulk, gamma-mutated being]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speciesAsRedHulk Context triple: [Thunderbolt Ross, speciesAsRedHulk, gamma-mutated being]
-
A.
speciesTypeInMarvel
chosen
Indicates that a given species is classified as a particular type of species within the Marvel universe.
-
B.
roleInAvengers
Indicates that an entity has a specific role or membership status within the Avengers team.
-
C.
relationshipToMarvelUniverse
Indicates the nature or type of connection an entity has to the Marvel universe, such as affiliation, role, or relevance within that fictional setting.
-
D.
hasSuperheroMantle
Indicates that one entity holds or has assumed the superhero identity, title, or role associated with another entity.
-
E.
hulked
Indicates a relationship where an entity became or appeared extremely large, muscular, or bulky, often in a sudden or dramatic way.
- 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_69d8d387b5548190aa030dad2cb4947e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e533f9bd1081909743b24e290b7dfe |
completed | April 19, 2026, 7:58 p.m. |
| PD | Predicate disambiguation | batch_69e469e0025c81908f16ed4f922674af |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:37 a.m.