Triple
T23067886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stheno |
E575101
|
entity |
| Predicate | threatLevelInMyth |
P61645
|
FINISHED |
| Object | extremelyDangerous |
—
|
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: extremelyDangerous | Statement: [Stheno, threatLevelInMyth, extremelyDangerous]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: threatLevelInMyth Context triple: [Stheno, threatLevelInMyth, extremelyDangerous]
-
A.
threatLevelDescription
chosen
Indicates a textual description that characterizes the severity or nature of a threat level associated with an entity or situation.
-
B.
threatInStory
Indicates that one entity poses or represents a danger, menace, or harmful intent toward another entity within the context of a narrative or story.
-
C.
threatType
Indicates the specific category or nature of a threat that one entity poses or represents in relation to another.
-
D.
threatCategory
Indicates the classification of a threat according to its type, severity, or nature within a defined risk or security framework.
-
E.
thrillLevel
Indicates the degree of excitement or intensity of exhilaration associated with an experience, action, or situation.
- 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_69e245bd6e4c8190bb8942245b68cad5 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f189a5aa4081909b3f0dc92877323d |
completed | April 29, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
Created at: April 17, 2026, 3:55 p.m.