Triple

T14602994
Position Surface form Disambiguated ID Type / Status
Subject Persian gardens E342748 entity
Predicate UNESCOSerialPropertyInscriptionYear P57323 FINISHED
Object 2011 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: 2011 | Statement: [Persian gardens, UNESCOSerialPropertyInscriptionYear, 2011]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: UNESCOSerialPropertyInscriptionYear
Context triple: [Persian gardens, UNESCOSerialPropertyInscriptionYear, 2011]
  • A. UNESCOWorldHeritageDesignationYear
    Indicates the year in which a site was officially designated as a UNESCO World Heritage site.
  • B. UNESCOSerialNomination
    Indicates that multiple geographically or culturally related sites are jointly nominated as a single serial property on the UNESCO World Heritage List.
  • C. inscribedOnUNESCOListInYear chosen
    Indicates that an entity was officially added to a UNESCO list (such as World Heritage) in a specified year.
  • D. UNESCOWorldHeritageSiteId
    Indicates that an entity is identified as a UNESCO World Heritage Site by a specific UNESCO World Heritage Site identifier.
  • E. UNESCOSessionOfInscription
    Indicates the specific UNESCO session during which an item was formally inscribed or added to a UNESCO list.
  • 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_69d822dec68081908c2553145c4051dc completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb43a1bb48190bf520cb961f15b5e completed April 14, 2026, 9:40 p.m.
PD Predicate disambiguation batch_69de656f9f4c81909f815b6629a9ee39 completed April 14, 2026, 4:03 p.m.
Created at: April 10, 2026, 1:25 a.m.