Triple
T14876903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Extremis |
E349889
|
entity |
| Predicate | influencedArmorDesign |
P44042
|
FINISHED |
| Object | Iron Man’s MCU armor aesthetics |
—
|
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: Iron Man’s MCU armor aesthetics | Statement: [Extremis, influencedArmorDesign, Iron Man’s MCU armor aesthetics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: influencedArmorDesign Context triple: [Extremis, influencedArmorDesign, Iron Man’s MCU armor aesthetics]
-
A.
armour
Indicates that an entity provides protective covering or defense for another entity.
-
B.
armorDesigner
Indicates that one entity is the designer or creator of another entity’s armor.
-
C.
designInfluenceOn
chosen
Indicates that one design, designer, or design-related factor has an effect on shaping, guiding, or altering another design or design outcome.
-
D.
armorType
Indicates the specific category or classification of protective armor associated with an entity.
-
E.
notableArmor
Indicates that an entity is recognized for possessing or being associated with armor of particular significance, prominence, or distinction.
- 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_69d822ee4f408190b6ac3b2fa434f0df |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded5e4e4448190a8796573bc6d1069 |
completed | April 15, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69de8c1a2bcc81908f914e2e2ced65eb |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:55 a.m.