Triple
T8450609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valkyrie (MCU) |
E199788
|
entity |
| Predicate | superhumanAbility |
P42064
|
FINISHED |
| Object | superhuman strength |
—
|
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: superhuman strength | Statement: [Valkyrie (MCU), superhumanAbility, superhuman strength]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: superhumanAbility Context triple: [Valkyrie (MCU), superhumanAbility, superhuman strength]
-
A.
hasSuperpower
chosen
Indicates that one entity possesses a special or extraordinary power or ability beyond normal human capabilities.
-
B.
notablePower
Indicates that an entity possesses a significant or distinguished form of power, influence, or capability that is recognized as noteworthy.
-
C.
forceAbility
Indicates that one entity has the power or capacity to compel, influence, or cause another entity to act or change in a particular way.
-
D.
enhancesPowersOf
Indicates that one entity increases, amplifies, or strengthens the abilities or powers of another entity.
-
E.
ultimateAbility
Indicates that an entity possesses or uses its most powerful, defining special ability or move.
- 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_69ca8318231881908fd1bc1c4d45d286 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe44815488190a912d63512e19af0 |
completed | March 31, 2026, 3:12 p.m. |
| PD | Predicate disambiguation | batch_69cbd0f5a3648190beb53a139a2d5482 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:09 p.m.