Triple
T12553637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mega-City One |
E300158
|
entity |
| Predicate | threatInFiction |
P95621
|
FINISHED |
| Object | mutant incursions from the Cursed Earth |
—
|
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: mutant incursions from the Cursed Earth | Statement: [Mega-City One, threatInFiction, mutant incursions from the Cursed Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: threatInFiction Context triple: [Mega-City One, threatInFiction, mutant incursions from the Cursed Earth]
-
A.
threatenedByInFiction
chosen
Indicates that, within a fictional context, one entity is portrayed as being threatened by another entity.
-
B.
threatType
Indicates the specific category or nature of a threat that one entity poses or represents in relation to another.
-
C.
threat
Indicates a relationship where one entity expresses or poses potential harm, danger, or negative consequences toward another entity.
-
D.
threatCategory
Indicates the classification of a threat according to its type, severity, or nature within a defined risk or security framework.
-
E.
threatDisplay
Indicates a behavior or signal by one entity intended to warn, intimidate, or deter another entity without immediate physical attack.
- 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_69d6ada707008190aaec1238117c9379 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95f5507b481908d13cc317b7402f6 |
completed | April 10, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69d95410d0b0819097646edd1b837104 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:58 p.m.