Triple
T30581427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antarctic Vibranium |
E778390
|
entity |
| Predicate | inUniverseRisk |
P178619
|
FINISHED |
| Object | threat to metal-based technology |
—
|
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: threat to metal-based technology | Statement: [Antarctic Vibranium, inUniverseRisk, threat to metal-based technology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseRisk Context triple: [Antarctic Vibranium, inUniverseRisk, threat to metal-based technology]
-
A.
AlexanderRisk
Indicates a relationship where Alexander is exposed to, associated with, or responsible for a particular risk or potential adverse outcome.
-
B.
riskBasis
Indicates the underlying factor, condition, or rationale that forms the basis for assessing or assigning risk in a given context.
-
C.
hasRiskFrom
Indicates that one entity is exposed to or may suffer potential harm, loss, or adverse effects as a result of another entity.
-
D.
riskToUser
Indicates that something poses a potential danger, harm, or adverse impact to the user.
-
E.
focusesOnRisk
Indicates that the subject directs attention, resources, or analysis primarily toward identifying, assessing, or managing risk.
- F. None of above. chosen
Provenance (4 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_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f7117cf2188190b29e36fc1e342c60 |
completed | May 3, 2026, 9:12 a.m. |
Created at: April 29, 2026, 8:23 p.m.