Triple
T3112212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hank Pym |
E64976
|
entity |
| Predicate | superpower |
P42064
|
FINISHED |
| Object | size reduction |
—
|
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: size reduction | Statement: [Hank Pym, superpower, size reduction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: superpower Context triple: [Hank Pym, superpower, size reduction]
-
A.
majorPowerIn
Indicates that an entity holds significant political, economic, or military influence within a specified domain, region, or context.
-
B.
majorPowerUntil
Indicates that an entity functioned as a major power or dominant force up to, but not beyond, a specified time or event.
-
C.
powers
Indicates that one entity supplies or provides the energy, authority, or driving force that enables another entity to function or operate.
-
D.
hasSuperpower
chosen
Indicates that one entity possesses a special or extraordinary power or ability beyond normal human capabilities.
-
E.
exclusivePower
Indicates that one entity holds sole authority or control over another entity or a specific domain, excluding others from sharing that power.
- 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_69ad857eeaf48190b34ebfdaa7a264cf |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada43b0b3c8190a828c9cfcf730ed9 |
completed | March 8, 2026, 4:30 p.m. |
| PD | Predicate disambiguation | batch_69ad9df25d4c81908ff0f6cff55d0563 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:04 p.m.