Triple

T19406637
Position Surface form Disambiguated ID Type / Status
Subject Kushika dynasty E485478 entity
Predicate functionInLiterature P135758 FINISHED
Object exemplifies ideal royal patrons of Vedic seers 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: exemplifies ideal royal patrons of Vedic seers | Statement: [Kushika dynasty, functionInLiterature, exemplifies ideal royal patrons of Vedic seers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: functionInLiterature
Context triple: [Kushika dynasty, functionInLiterature, exemplifies ideal royal patrons of Vedic seers]
  • A. inLiterature
    Indicates that a work, concept, or entity is mentioned, discussed, or represented within a piece of literature.
  • B. literarySubject
    Indicates that one entity serves as the subject, topic, or focus of a literary work created by another entity.
  • C. languageWithinFiction
    Indicates that a language is used or exists within the context of a fictional work or fictional universe.
  • D. literaryFeature
    Indicates a relationship where something possesses or exhibits a characteristic, device, or stylistic element used in literature.
  • E. nameInLiterature
    Indicates that a particular name is used or appears for an entity within a literary work or 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_69d8e8d5162481909db12435d9535c1a completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e6257bad0c819088dd7729b6a36a94 completed April 20, 2026, 1:09 p.m.
PD Predicate disambiguation batch_69e4fd68b1f881908d273de1fee81a75 completed April 19, 2026, 4:06 p.m.
PDg Predicate description generation batch_69e5004c23308190a087b7941a90725f completed April 19, 2026, 4:18 p.m.
Created at: April 10, 2026, 1:36 p.m.