Triple

T27182065
Position Surface form Disambiguated ID Type / Status
Subject Tinum Municipality E683220 entity
Predicate hasArchaeologicalTourism P173353 FINISHED
Object Chichén Itzá tourism 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: Chichén Itzá tourism | Statement: [Tinum Municipality, hasArchaeologicalTourism, Chichén Itzá tourism]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasArchaeologicalTourism
Context triple: [Tinum Municipality, hasArchaeologicalTourism, Chichén Itzá tourism]
  • A. hasArchitecturalSite
    Indicates that an entity possesses, contains, or is associated with a specific architectural site.
  • B. hasArchaeologicalParkStatus
    Indicates that an entity has been officially designated and recognized as an archaeological park.
  • C. hasArchaeologicalCulture
    Indicates that an entity is associated with, belongs to, or is characterized by a particular archaeological culture.
  • D. hasArchaeologicalExcavationsBy
    Indicates that archaeological excavations at a site or location are or were conducted by a specified person, group, or organization.
  • E. hasArchaeologicalSitesFrom
    Indicates that an entity contains or is associated with archaeological sites dating from a specified time period or era.
  • F. None of above. chosen

Provenance (4 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_69eefad140408190b8586fdebcf9af46 completed April 27, 2026, 5:57 a.m.
NER Named-entity recognition batch_69f6b56ed31481908c3e5d749e46bad9 completed May 3, 2026, 2:39 a.m.
PD Predicate disambiguation batch_69f6b3a5fd8481909433e923c5e24e55 completed May 3, 2026, 2:32 a.m.
PDg Predicate description generation batch_69f6b49339048190b617a6749f648825 completed May 3, 2026, 2:36 a.m.
Created at: April 27, 2026, 9:28 a.m.