Triple
T14876895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Extremis |
E349889
|
entity |
| Predicate | givesAbility |
P67649
|
FINISHED |
| Object | direct neural interface with Iron Man armor |
—
|
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: direct neural interface with Iron Man armor | Statement: [Extremis, givesAbility, direct neural interface with Iron Man armor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: givesAbility Context triple: [Extremis, givesAbility, direct neural interface with Iron Man armor]
-
A.
grantsAbility
chosen
Indicates that one entity endows another entity with a specific capability or power that it did not previously possess.
-
B.
hasProtagonistAbility
Indicates that a protagonist possesses a specific ability, power, or special skill.
-
C.
grantedTalentBy
Indicates that a talent, skill, or special ability is conferred upon an entity by another entity as the granting source.
-
D.
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.
-
E.
symbolicAbility
Indicates the capacity of an entity to understand, manipulate, or use symbols to represent concepts, objects, or relationships.
- 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.