Triple

T15572876
Position Surface form Disambiguated ID Type / Status
Subject Other Franciscan Sites E374290 entity
Predicate UNESCOPropertyId P2117 FINISHED
Object 990 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: 990 | Statement: [Other Franciscan Sites, UNESCOPropertyId, 990]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: UNESCOPropertyId
Context triple: [Other Franciscan Sites, UNESCOPropertyId, 990]
  • A. UNESCOWorldHeritageSiteId chosen
    Indicates that an entity is identified as a UNESCO World Heritage Site by a specific UNESCO World Heritage Site identifier.
  • 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. UNESCOHeritage
    Indicates that a place, site, or cultural/natural asset has been officially inscribed on the UNESCO World Heritage List as having outstanding universal value.
  • D. UNESCOWorldHeritageDesignationYear
    Indicates the year in which a site was officially designated as a UNESCO World Heritage site.
  • E. UNESCOSiteType
    Indicates the classification of a UNESCO World Heritage Site according to its type (e.g., cultural, natural, or mixed).
  • 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_69d85ccd575081908909b71a3f3e3a61 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04e2025888190a2b6240296bba13e completed April 16, 2026, 2:49 a.m.
PD Predicate disambiguation batch_69deda7e6e748190b29ccce23298afef completed April 15, 2026, 12:23 a.m.
Created at: April 10, 2026, 4:10 a.m.