Triple

T38277723
Position Surface form Disambiguated ID Type / Status
Subject Al-Muʿallaqāt E1022004 entity
Predicate compilerTradition P128152 FINISHED
Object Hammad al-Rāwiya NE NERFINISHED

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: Hammad al-Rāwiya | Statement: [Al-Muʿallaqāt, compilerTradition, Hammad al-Rāwiya]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: compilerTradition
Context triple: [Al-Muʿallaqāt, compilerTradition, Hammad al-Rāwiya]
  • A. compilerType
    Indicates the specific kind or category of compiler associated with or used by an entity.
  • B. compilerFamily
    Indicates that one compiler belongs to, or is categorized under, a particular family or lineage of related compilers.
  • C. compilerLanguage
    Indicates that one entity is the programming language in which a given compiler is implemented.
  • D. compiledByTradition chosen
    Indicates that something has been assembled, organized, or codified according to established customs, practices, or traditional authority rather than by a single identifiable author.
  • E. formerCompiler
    Indicates that an entity previously served as a compiler (e.g., of texts, code, or documents) for another entity but no longer holds that role.
  • 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_69f76df0cddc81908d16c1556ff4097f completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fccbd826708190b5fab12c4236299a completed May 7, 2026, 5:28 p.m.
PD Predicate disambiguation batch_69fcc58838e08190b8fa54aa5c165f2d completed May 7, 2026, 5:02 p.m.
Created at: May 3, 2026, 4:30 p.m.