Triple

T8511022
Position Surface form Disambiguated ID Type / Status
Subject Ancient Thebes with its Necropolis E201451 entity
Predicate UNESCOSiteArea P80048 FINISHED
Object about 7,390 ha 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: about 7,390 ha | Statement: [Ancient Thebes with its Necropolis, UNESCOSiteArea, about 7,390 ha]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: UNESCOSiteArea
Context triple: [Ancient Thebes with its Necropolis, UNESCOSiteArea, about 7,390 ha]
  • A. UNESCODesignationArea
    Indicates that a specified geographic area has been formally designated or recognized by UNESCO under one of its official programs or lists.
  • B. UNESCOWorldHeritageAreaHa chosen
    Indicates that an area is designated as a UNESCO World Heritage site and specifies its size in hectares.
  • C. UNESCOSiteType
    Indicates the classification of a UNESCO World Heritage Site according to its type (e.g., cultural, natural, or mixed).
  • D. UNESCOCoreZoneArea
    Indicates the area encompassed by the core (legally protected) zone of a UNESCO-designated site.
  • E. UNESCOWorldHeritageSiteWithin
    Indicates that a UNESCO World Heritage Site is geographically located within the boundaries of a specified area or region.
  • 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_69ca8320e5748190ac2c585a0bba8193 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbe608e5b08190a6d551793e8ed94b completed March 31, 2026, 3:19 p.m.
PD Predicate disambiguation batch_69cbd10cfd208190a519049fad32c508 completed March 31, 2026, 1:50 p.m.
Created at: March 30, 2026, 6:15 p.m.