Triple
T17146999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shikishima |
E416115
|
entity |
| Predicate | stylisticEffect |
P126291
|
FINISHED |
| Object | elevated tone |
—
|
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: elevated tone | Statement: [Shikishima, stylisticEffect, elevated tone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stylisticEffect Context triple: [Shikishima, stylisticEffect, elevated tone]
-
A.
stylisticFocus
Indicates a relationship where something is primarily concerned with, emphasizes, or is characterized by a particular style or set of stylistic features.
-
B.
stylisticSignificance
Indicates that one entity holds importance or meaning specifically because of its style or manner of expression in relation to another entity or context.
-
C.
stylisticRange
Indicates the range or spectrum of styles that characterize or can be applied to something.
-
D.
stylisticShiftDirection
Indicates the direction or nature of a change in style from one state, work, or expression to another.
-
E.
characterStyle
Indicates how a character is visually or typographically presented, such as its font, weight, size, or decorative attributes.
- F. None of above. chosen
Provenance (4 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f2db20d48190b5d69ccf89f3bc42 |
completed | April 18, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_69e3830d2a90819092386717dc56f0e8 |
completed | April 18, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69e3873f62108190966c4e741ebd548d |
completed | April 18, 2026, 1:29 p.m. |
Created at: April 10, 2026, 5:36 a.m.