Triple

T9797434
Position Surface form Disambiguated ID Type / Status
Subject Ministry of the Interior building (Havana) E237751 entity
Predicate hasTouristSignificance P530 FINISHED
Object yes — 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: yes | Statement: [Ministry of the Interior building (Havana), hasTouristSignificance, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTouristSignificance
Context triple: [Ministry of the Interior building (Havana), hasTouristSignificance, yes]
  • A. hasTouristAttractionRole
    Indicates that an entity serves in the capacity or function of a tourist attraction for another entity (such as a place, organization, or area).
  • B. hasTouristSignage
    Indicates that there is official signage present to guide or inform tourists about a place, route, or attraction.
  • C. hasTouristRank
    Indicates that an entity is assigned a specific rank or rating based on its attractiveness or importance as a tourist destination.
  • D. isTouristDestination chosen
    Indicates that a place is recognized as a location people commonly visit for leisure, sightseeing, or travel.
  • E. hasHistoricalSignificance
    Indicates that something possesses notable importance or influence within a historical context or period.
  • 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_69ca84dc04488190b9c91193976c0960 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cda6264160819080da4805b213753f completed April 1, 2026, 11:11 p.m.
PD Predicate disambiguation batch_69cd03da45a88190b71b1be3354c15a6 completed April 1, 2026, 11:39 a.m.
Created at: March 30, 2026, 8:28 p.m.