Triple

T8616530
Position Surface form Disambiguated ID Type / Status
Subject A History of Literary Criticism in the Renaissance E204052 entity
Predicate literaryCriticismType P83910 FINISHED
Object historical survey 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: historical survey | Statement: [A History of Literary Criticism in the Renaissance, literaryCriticismType, historical survey]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: literaryCriticismType
Context triple: [A History of Literary Criticism in the Renaissance, literaryCriticismType, historical survey]
  • A. literarySubject
    Indicates that one entity serves as the subject, topic, or focus of a literary work created by another entity.
  • B. literaryGenreOfWork
    Indicates that a work belongs to or is classified under a particular literary genre.
  • C. literaryGenreOfSourceWork
    Indicates that a work belongs to, or is characterized by, a particular literary genre.
  • D. literaryFeature
    Indicates a relationship where something possesses or exhibits a characteristic, device, or stylistic element used in literature.
  • E. literaryInterest
    Indicates that one entity has an interest in, appreciation of, or engagement with the literary works or writings of 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_69ca832ceab8819096e4a9f546695079 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cc4703b57c81909511de72fa5c38d7 completed March 31, 2026, 10:13 p.m.
PD Predicate disambiguation batch_69cc455437488190b7506f820daf6e32 completed March 31, 2026, 10:06 p.m.
PDg Predicate description generation batch_69cc46c330bc8190a9b644078881c6ff completed March 31, 2026, 10:12 p.m.
Created at: March 30, 2026, 6:25 p.m.