Triple

T28143604
Position Surface form Disambiguated ID Type / Status
Subject Municipality of Guatavita E714414 entity
Predicate hasNearbyIndigenousSacredSite P32871 FINISHED
Object Lake Guatavita NE NERFINISHED

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: Lake Guatavita | Statement: [Municipality of Guatavita, hasNearbyIndigenousSacredSite, Lake Guatavita]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNearbyIndigenousSacredSite
Context triple: [Municipality of Guatavita, hasNearbyIndigenousSacredSite, Lake Guatavita]
  • A. hasNearbyPilgrimageSite
    Indicates that one entity is located close to a place used as a pilgrimage site for religious or spiritual journeys.
  • B. nearbyIndigenousHeritage chosen
    Indicates that an entity is located close to a site, area, or feature of Indigenous cultural, historical, or spiritual heritage.
  • C. hasSacredPrecinct
    Indicates that an entity possesses or contains a designated sacred area or precinct associated with religious or ritual significance.
  • D. hasTribalHeadquartersNearby
    Indicates that the subject entity is located close to the tribal headquarters of a Native nation or tribe.
  • E. hasNearbyArchaeologicalSite
    Indicates that an entity is located close to or in the vicinity of an archaeological site.
  • 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_69efd6b033208190bf74f80a147e2092 completed April 27, 2026, 9:35 p.m.
NER Named-entity recognition batch_69fd64bc86848190a49f451a8fc5cf1e completed May 8, 2026, 4:21 a.m.
PD Predicate disambiguation batch_69fd5ff4a648819090756d90fd195d9a completed May 8, 2026, 4 a.m.
Created at: April 27, 2026, 9:55 p.m.