Triple
T10219672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dork Elvis |
E242540
|
entity |
| Predicate | characterizesStyleAs |
P48733
|
FINISHED |
| Object | data-driven |
—
|
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: data-driven | Statement: [Dork Elvis, characterizesStyleAs, data-driven]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterizesStyleAs Context triple: [Dork Elvis, characterizesStyleAs, data-driven]
-
A.
styleDescribedAs
chosen
Indicates that the manner, aesthetic, or mode of something is characterized or labeled using a particular style description.
-
B.
styleTendsTo
Indicates that one style is generally inclined or likely to develop, appear, or be adopted in the direction of another style.
-
C.
characterStyle
Indicates how a character is visually or typographically presented, such as its font, weight, size, or decorative attributes.
-
D.
notableWorkStyle
Indicates a stylistic characteristic or distinctive manner associated with a notable work created by the subject.
-
E.
conveysStyle
Indicates that one entity expresses, communicates, or embodies a particular style through its form, behavior, or presentation.
- 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_69d381ae26c48190985abd0e25ee5d04 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d3aa715a3c8190a9ccee7bcece0346 |
completed | April 6, 2026, 12:43 p.m. |
| PD | Predicate disambiguation | batch_69d3955f61f88190b8d37ff645cd44d3 |
completed | April 6, 2026, 11:13 a.m. |
Created at: April 6, 2026, 11:08 a.m.