Triple

T11400319
Position Surface form Disambiguated ID Type / Status
Subject Epistolae obscurorum virorum E270089 entity
Predicate hasFictionalAuthors P68311 FINISHED
Object obscure theologians 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: obscure theologians | Statement: [Epistolae obscurorum virorum, hasFictionalAuthors, obscure theologians]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFictionalAuthors
Context triple: [Epistolae obscurorum virorum, hasFictionalAuthors, obscure theologians]
  • A. hasFictionalAuthor chosen
    Indicates that one entity is the fictional or in-universe author of a work attributed to them.
  • B. hasFictionalWork
    Indicates that one entity is the creator, owner, or source of a fictional work associated with another entity.
  • C. hasFictionalEditor
    Indicates that an entity is associated with a fictional editor character responsible for editing or overseeing its content within a narrative or fictional context.
  • D. hasFictionalContent
    Indicates that something contains or includes material that is imaginary, invented, or not intended to represent real events or facts.
  • E. hasFictionalPerformer
    Indicates that an entity is associated with a performer who is a fictional or imaginary character rather than a real person.
  • 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_69d6aacdbc6c8190af6dc3d5f5d22836 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d8001adc188190ae45227856156412 completed April 9, 2026, 7:38 p.m.
PD Predicate disambiguation batch_69d7e70b228c8190b87f5101fd683788 completed April 9, 2026, 5:51 p.m.
Created at: April 8, 2026, 9:34 p.m.