Triple
T12887956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teofil Lenartowicz |
E308277
|
entity |
| Predicate | creativeWorkStyle |
P1851
|
FINISHED |
| Object | folk-inspired poetry |
—
|
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: folk-inspired poetry | Statement: [Teofil Lenartowicz, creativeWorkStyle, folk-inspired poetry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creativeWorkStyle Context triple: [Teofil Lenartowicz, creativeWorkStyle, folk-inspired poetry]
-
A.
notableWorkStyle
Indicates a stylistic characteristic or distinctive manner associated with a notable work created by the subject.
-
B.
artisticStyle
chosen
Indicates the artistic movement, style, or aesthetic approach that characterizes how something is created or visually expressed.
-
C.
productionDesignStyle
Indicates the visual and aesthetic approach used in designing the overall look and environment of a production.
-
D.
creativeOutput
Indicates that an entity produces, originates, or is responsible for a creative work or result.
-
E.
creativeMethod
Indicates the technique, approach, or process used to produce or carry out a creative work or activity.
- 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97c7f91d08190aac2f6419d3ba992 |
completed | April 10, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69d96fa55b888190ab1612e93c41aec4 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:39 p.m.