Triple

T7186704
Position Surface form Disambiguated ID Type / Status
Subject Salt Cathedral of Zipaquirá E167589 entity
Predicate originalCathedralClosed P75895 FINISHED
Object 1990 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: 1990 | Statement: [Salt Cathedral of Zipaquirá, originalCathedralClosed, 1990]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: originalCathedralClosed
Context triple: [Salt Cathedral of Zipaquirá, originalCathedralClosed, 1990]
  • A. containsCathedral
    Indicates that one entity includes or has within its boundaries a cathedral associated with it.
  • B. cathedralChurch
    Indicates that one church serves as the cathedral (principal church and episcopal seat) of another ecclesiastical jurisdiction or entity.
  • C. cathedral
    Indicates that an entity is a cathedral, i.e., it has the status or function of a principal church, typically one that is the seat of a bishop.
  • D. cathedralStatus
    Indicates that an entity holds the official status or designation of a cathedral within a religious or ecclesiastical context.
  • E. coCathedral
    Indicates that a church shares the status and functions of a cathedral with another cathedral within the same diocese or ecclesiastical jurisdiction.
  • 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_69c6888b5248819090499a884ee3ec39 completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6e9b045c48190b27b2d6f7c11026f completed March 27, 2026, 8:33 p.m.
PD Predicate disambiguation batch_69c6e74fb0f48190b2ad4dd4efdd241a completed March 27, 2026, 8:23 p.m.
PDg Predicate description generation batch_69c6e9aeb1b08190ace6f978387c89aa completed March 27, 2026, 8:33 p.m.
Created at: March 27, 2026, 2:49 p.m.