Triple
T30056886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Superman villains |
E763755
|
entity |
| Predicate | commonWeaknessExploited |
P119540
|
FINISHED |
| Object | Kryptonite |
—
|
NE NERFINISHED |
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: Kryptonite | Statement: [Superman villains, commonWeaknessExploited, Kryptonite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonWeaknessExploited Context triple: [Superman villains, commonWeaknessExploited, Kryptonite]
-
A.
canBeExploitedFor
Indicates that one entity is capable of being used or taken advantage of by another entity to obtain some benefit, resource, or outcome.
-
B.
CVEIdentifier
Indicates that an entity is associated with a specific Common Vulnerabilities and Exposures (CVE) identifier, uniquely referencing a documented security vulnerability.
-
C.
vulnerabilityType
Indicates the specific kind or category of vulnerability associated with an entity or situation.
-
D.
vulnerabilitySource
chosen
Indicates that one entity is the origin, cause, or contributing factor of another entity’s vulnerability or weakness.
-
E.
earlyExploitationBy
Indicates that one entity takes unfair advantage of another at an early stage of their interaction, development, or process.
- 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_69f224716378819087a722e487832b70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd783fed9c81909e792702636c4f1f |
completed | May 8, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69fd7788e63c81909de22fdafcfe41c0 |
completed | May 8, 2026, 5:41 a.m. |
Created at: April 29, 2026, 6:56 p.m.