Triple
T27525180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish Classicism |
E694812
|
entity |
| Predicate | typicalLiteraryForms |
P201047
|
FINISHED |
| Object | ode |
—
|
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: ode | Statement: [Polish Classicism, typicalLiteraryForms, ode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLiteraryForms Context triple: [Polish Classicism, typicalLiteraryForms, ode]
-
A.
hasLiteraryForm
Indicates that one entity is expressed, structured, or realized in a particular literary form (such as a genre, style, or textual format).
-
B.
literaryTradition
Indicates a relationship where a work, practice, or expression belongs to, arises from, or participates in a particular established body of literary customs, styles, or conventions.
-
C.
literaryFeature
Indicates a relationship where something possesses or exhibits a characteristic, device, or stylistic element used in literature.
-
D.
literaryGenreOfWork
Indicates that a work belongs to or is classified under a particular literary genre.
-
E.
literarySubject
Indicates that one entity serves as the subject, topic, or focus of a literary work created by another entity.
- 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_69ef538550208190aa9de8e2cb260d93 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69ffc516d1908190b475f5a6156b0ca8 |
completed | May 9, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69ffc4a946e08190b3535a5dc15ac484 |
completed | May 9, 2026, 11:35 p.m. |
| PDg | Predicate description generation | batch_69ffc515e4b08190810b2a29b2885162 |
completed | May 9, 2026, 11:36 p.m. |
Created at: April 27, 2026, 1:23 p.m.