Triple
T10626373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naiads |
E250333
|
entity |
| Predicate | dangerAspect |
P50110
|
FINISHED |
| Object | could drown mortals |
—
|
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: could drown mortals | Statement: [Naiads, dangerAspect, could drown mortals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dangerAspect Context triple: [Naiads, dangerAspect, could drown mortals]
-
A.
dangerWarning
Indicates that one entity issues or represents a warning about potential danger associated with another entity or situation.
-
B.
threatType
chosen
Indicates the specific category or nature of a threat that one entity poses or represents in relation to another.
-
C.
threatCategory
Indicates the classification of a threat according to its type, severity, or nature within a defined risk or security framework.
-
D.
dangerousWhen
Indicates that one entity becomes harmful, risky, or unsafe under the conditions or in the presence of another entity or situation.
-
E.
warningType
Indicates the specific category or classification of a warning associated with an entity or event.
- 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6df80a30c81909f36fe221cf68822 |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7fae088190973f70c69738af49 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 8:55 p.m.