Triple
T36697639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terrigen Mists |
E906133
|
entity |
| Predicate | effectOnInhumans |
P165023
|
FINISHED |
| Object | unlock latent superhuman abilities |
—
|
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: unlock latent superhuman abilities | Statement: [Terrigen Mists, effectOnInhumans, unlock latent superhuman abilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnInhumans Context triple: [Terrigen Mists, effectOnInhumans, unlock latent superhuman abilities]
-
A.
effectOnRace
chosen
Indicates that one entity has an influence or impact on the outcome, dynamics, or characteristics of a race.
-
B.
heroPowerEffect
Indicates the specific impact or outcome that a hero’s power has when it is used.
-
C.
effectOnOthers
Indicates the impact or influence that one entity’s actions, presence, or state has on other entities.
-
D.
effectOnUser
Indicates how an action, event, or condition influences or impacts a user.
-
E.
effectOnSystem
Indicates the influence, change, or impact that one entity, action, or condition has on the state or behavior of a system.
- 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_69f76e7195c48190b5580c9cfb01e95f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fdb45537288190b6791078d4a6899f |
completed | May 8, 2026, 10 a.m. |
| PD | Predicate disambiguation | batch_69fdb39ad96481908376d7def9fafc13 |
completed | May 8, 2026, 9:57 a.m. |
Created at: May 3, 2026, 4:12 p.m.