Triple

T2177253
Position Surface form Disambiguated ID Type / Status
Subject Cynthia E48557 entity
Predicate hasLiteraryUsage P29936 FINISHED
Object English 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: English poetry | Statement: [Cynthia, hasLiteraryUsage, English poetry]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLiteraryUsage
Context triple: [Cynthia, hasLiteraryUsage, English poetry]
  • A. hasLiterarySignificance
    Indicates that something holds notable importance, influence, or value within the realm of literature or literary studies.
  • B. hasLiteraryForm
    Indicates that one entity is expressed, structured, or realized in a particular literary form (such as a genre, style, or textual format).
  • C. hasLiteraryConnection chosen
    Indicates a relationship in which one entity is connected to another through a literary link, such as authorship, reference, influence, adaptation, or shared appearance in written works.
  • D. hasLiteraryStandard
    Indicates that one entity defines, specifies, or embodies the accepted literary norm or standard used by another entity.
  • E. literaryLanguage
    Indicates that an entity is expressed, written, or communicated using a particular literary or standardized written language.
  • 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_69a88aa3faa48190995b233af6525815 completed March 4, 2026, 7:40 p.m.
NER Named-entity recognition batch_69abc4358fc88190a6f556c2de9fef8c completed March 7, 2026, 6:22 a.m.
PD Predicate disambiguation batch_69abbda0ec948190be88c1243d81a423 completed March 7, 2026, 5:54 a.m.
Created at: March 4, 2026, 7:45 p.m.