Triple

T29246217
Position Surface form Disambiguated ID Type / Status
Subject Roman theater of Bosra E741446 entity
Predicate heritageInDangerSince P122939 FINISHED
Object 2013 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: 2013 | Statement: [Roman theater of Bosra, heritageInDangerSince, 2013]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: heritageInDangerSince
Context triple: [Roman theater of Bosra, heritageInDangerSince, 2013]
  • A. heritageThreat
    Indicates that an entity poses a risk of damage, loss, or degradation to cultural, historical, or natural heritage.
  • B. UNESCOdangerListInscriptionYear chosen
    Indicates the year in which a site was inscribed on UNESCO’s List of World Heritage in Danger.
  • C. UNESCOEndangermentCategory
    Indicates the level of endangerment assigned to a language according to UNESCO’s classification system.
  • D. addedToListOfWorldHeritageInDanger
    Indicates that a site has been officially placed on the List of World Heritage in Danger, recognizing it as threatened and in need of special protection or conservation measures.
  • E. heritageProtectionIssues
    Indicates that there are concerns, conflicts, or regulatory constraints related to the protection or preservation of cultural, historical, or natural heritage associated with the entities.
  • 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_69f0911eba2c8190b07cd2fdf91422c9 completed April 28, 2026, 10:51 a.m.
NER Named-entity recognition batch_69f72921cf2c8190909bb53f78bcc890 completed May 3, 2026, 10:53 a.m.
PD Predicate disambiguation batch_69f7283d8cec8190b524c144948bc4ec completed May 3, 2026, 10:49 a.m.
Created at: April 28, 2026, 12:32 p.m.