Triple
T13508060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 10,000 Volt Ghost |
E321062
|
entity |
| Predicate | threatLevelInSeries |
P27859
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [10,000 Volt Ghost, threatLevelInSeries, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: threatLevelInSeries Context triple: [10,000 Volt Ghost, threatLevelInSeries, high]
-
A.
threatLevelDescription
Indicates a textual description that characterizes the severity or nature of a threat level associated with an entity or situation.
-
B.
threatType
Indicates the specific category or nature of a threat that one entity poses or represents in relation to another.
-
C.
thrillLevel
Indicates the degree of excitement or intensity of exhilaration associated with an experience, action, or situation.
-
D.
threatCategory
Indicates the classification of a threat according to its type, severity, or nature within a defined risk or security framework.
-
E.
threatStatus
chosen
Indicates the level or category of risk or danger posed by one entity to another or to a defined system or environment.
- 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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf85a74081909eb08751fc55ce8f |
completed | April 12, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69dbae0b63748190b5e207f84b2532ea |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:43 p.m.