Triple
T14239827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marvel's Iron Fist |
E352975
|
entity |
| Predicate | characterPower |
P99992
|
FINISHED |
| Object | mystical Iron Fist |
—
|
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: mystical Iron Fist | Statement: [Marvel's Iron Fist, characterPower, mystical Iron Fist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterPower Context triple: [Marvel's Iron Fist, characterPower, mystical Iron Fist]
-
A.
heroPower
chosen
Indicates that an entity possesses or is associated with a particular heroic power or special ability.
-
B.
protagonistCharacteristic
Indicates that a characteristic, trait, or defining quality is attributed to the protagonist in a narrative or scenario.
-
C.
associatedCharacterTrait
Indicates a relationship where a character is linked to, or described by, a particular trait or quality.
-
D.
notableTraitInMarvel
Indicates that a particular trait or characteristic is especially prominent or noteworthy within the Marvel universe.
-
E.
featuresCharacterWith
Indicates that one entity (such as a work or product) includes or presents a particular character as part of its content.
- 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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de62432fb48190b153805b85c4f2d2 |
completed | April 14, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69de05bf069c8190b69f00f00f5eb126 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:08 a.m.