Triple
T17343221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian Silver Age culture |
E421115
|
entity |
| Predicate | periodFollowed |
P20651
|
FINISHED |
| Object | Russian Golden Age literature |
—
|
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: Russian Golden Age literature | Statement: [Russian Silver Age culture, periodFollowed, Russian Golden Age literature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: periodFollowed Context triple: [Russian Silver Age culture, periodFollowed, Russian Golden Age literature]
-
A.
eraFollowed
chosen
Indicates that one historical era comes directly after another in chronological sequence.
-
B.
followsTime
Indicates that one event, state, or time period occurs after and in temporal succession to another.
-
C.
followedIn
Indicates that one entity began following or subscribing to another entity, typically in a social or sequential context.
-
D.
followsDisc
Indicates that one entity comes after another in a sequence or order, typically in a discrete or stepwise progression.
-
E.
followerOf
Indicates that one entity subscribes to, tracks, or regularly receives updates from another entity, typically in a social or informational context.
- 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_69d889d3adc881909319f1edb8d2a956 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a18aca88190a816da85dd5fe371 |
completed | April 19, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b021a5bc81909ae55406f9d0b37f |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:44 a.m.