Triple
T20605297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mordwand |
E506290
|
entity |
| Predicate | hasNameConnotation |
P4340
|
FINISHED |
| Object | ominous |
—
|
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: ominous | Statement: [Mordwand, hasNameConnotation, ominous]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameConnotation Context triple: [Mordwand, hasNameConnotation, ominous]
-
A.
hasConnotation
chosen
Indicates that one entity carries an implied or associated meaning, tone, or emotional nuance in relation to another entity.
-
B.
hasPositiveConnotation
Indicates that something is associated with favorable, pleasant, or approving meanings, feelings, or implications.
-
C.
hasPejorativeName
Indicates that an entity is referred to by a name or label that carries a negative, derogatory, or disparaging connotation.
-
D.
honorificConnotation
Indicates that one entity refers to or characterizes another using an honorific or respectful form, conveying deference or elevated social status.
-
E.
hasNameMeaningRelation
Indicates that there is a relationship between an entity and a name that conveys or encodes a particular meaning or significance.
- 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_69e0b4bb2b4081908fa4a72444120f35 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aa2452888190858d273430cd783d |
completed | April 20, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69e5a00c43308190b7ea58d559257e07 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:41 a.m.