Triple

T13361612
Position Surface form Disambiguated ID Type / Status
Subject Georgian literature E318832 entity
Predicate notableMedievalGenre P109621 FINISHED
Object courtly epic 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: courtly epic | Statement: [Georgian literature, notableMedievalGenre, courtly epic]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: notableMedievalGenre
Context triple: [Georgian literature, notableMedievalGenre, courtly epic]
  • A. isMedieval
    Indicates that something belongs to, originates from, or is characteristic of the medieval (Middle Ages) period.
  • B. positionOnMedievalism
    Indicates a stance, view, or attitude that an entity holds regarding medievalism as a concept, movement, or interpretive framework.
  • C. medievalSeeTransferredTo
    Indicates that authority, ownership, or jurisdiction over a medieval ecclesiastical see was formally transferred from one holder or location to another.
  • D. medievalStatus
    Indicates the social, legal, or hierarchical standing an entity holds within a medieval societal structure.
  • E. medievalLordship
    Indicates a feudal relationship in which one entity holds authority, control, or dominion over another in a medieval lord–vassal or territorial context.
  • 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_69d806b7bbac8190b85278c87fa7aff3 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69da628affd081909f1790d333f0eef4 completed April 11, 2026, 3:02 p.m.
PD Predicate disambiguation batch_69d9a02c9abc8190b328e7bae747bfc5 completed April 11, 2026, 1:13 a.m.
PDg Predicate description generation batch_69dadcce5a808190847f2a7833b67a5a completed April 11, 2026, 11:44 p.m.
Created at: April 9, 2026, 9:32 p.m.