Triple
T26166253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian classicism |
E654258
|
entity |
| Predicate | majorFigureInLiterature |
P178757
|
FINISHED |
| Object | Alexander Sumarokov |
—
|
NE NERFINISHED |
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: Alexander Sumarokov | Statement: [Russian classicism, majorFigureInLiterature, Alexander Sumarokov]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorFigureInLiterature Context triple: [Russian classicism, majorFigureInLiterature, Alexander Sumarokov]
-
A.
nameInLiterature
Indicates that a particular name is used or appears for an entity within a literary work or context.
-
B.
literaryCharacterModeledAs
Indicates that one literary character is created or portrayed based on the traits, life, or persona of another real or fictional individual.
-
C.
literaryAuthor
Indicates that one entity is the author or writer of a literary work represented by the other entity.
-
D.
literaryRole
Indicates the specific narrative or functional role an entity holds within a literary work or text.
-
E.
characterInLiteraryMovement
Indicates that a character is associated with, or exemplifies the traits of, a particular literary movement.
- 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_69ee5b44391c81908bdbd8813ba9aa99 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69f71421e8d08190807ccfb15d0f0ddb |
completed | May 3, 2026, 9:23 a.m. |
Created at: April 26, 2026, 8:32 p.m.