Triple

T9164829
Position Surface form Disambiguated ID Type / Status
Subject Asad E219923 entity
Predicate usedInLiteraryTradition P2989 FINISHED
Object Urdu 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: Urdu poetry | Statement: [Asad, usedInLiteraryTradition, Urdu poetry]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedInLiteraryTradition
Context triple: [Asad, usedInLiteraryTradition, Urdu poetry]
  • A. literaryTradition chosen
    Indicates a relationship where a work, practice, or expression belongs to, arises from, or participates in a particular established body of literary customs, styles, or conventions.
  • B. hasAncientLiteraryTradition
    Indicates that an entity possesses a long-established, historically significant body of written literature originating in ancient times.
  • C. hasLiterarySignificance
    Indicates that something holds notable importance, influence, or value within the realm of literature or literary studies.
  • D. hasUseInTradition
    Indicates that something is employed or holds a functional role within a particular cultural, religious, or historical tradition.
  • E. traditionallyLitAt
    Indicates that something is customarily illuminated by something else according to tradition or established practice.
  • 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_69ca83e3633c81908688a9fa2306ba99 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69ccaa2ee64c8190a9a5abafe5d0b086 completed April 1, 2026, 5:16 a.m.
PD Predicate disambiguation batch_69cc6605c6808190a30d92da006206ac completed April 1, 2026, 12:25 a.m.
Created at: March 30, 2026, 7:22 p.m.