Triple
T30581408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antarctic Vibranium |
E778390
|
entity |
| Predicate | effectOnVibranium |
P180540
|
FINISHED |
| Object | can destroy other vibranium |
—
|
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: can destroy other vibranium | Statement: [Antarctic Vibranium, effectOnVibranium, can destroy other vibranium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnVibranium Context triple: [Antarctic Vibranium, effectOnVibranium, can destroy other vibranium]
-
A.
effectOnMetals
chosen
Indicates the type or nature of influence that something has on metals, such as altering their properties, behavior, or state.
-
B.
heroPowerEffect
Indicates the specific impact or outcome that a hero’s power has when it is used.
-
C.
effectOnNativeResistance
Indicates the impact that one entity has on the level or strength of another entity’s native resistance.
-
D.
involvedPhysicalEffect
Indicates that one entity participates in causing, experiencing, or mediating a physical effect on another entity or the environment.
-
E.
ultimateEffect
Indicates the final or overall outcome that results from a preceding action, condition, or sequence of events.
- 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_69f224a04b248190b0ca443ec86207b8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 29, 2026, 8:23 p.m.