Triple
T1859921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hotel Nacional de Cuba |
E41790
|
entity |
| Predicate | hasOnsiteMuseum |
P16135
|
FINISHED |
| Object | exhibition on Cuban Missile Crisis bunkers |
—
|
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: exhibition on Cuban Missile Crisis bunkers | Statement: [Hotel Nacional de Cuba, hasOnsiteMuseum, exhibition on Cuban Missile Crisis bunkers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnsiteMuseum Context triple: [Hotel Nacional de Cuba, hasOnsiteMuseum, exhibition on Cuban Missile Crisis bunkers]
-
A.
hasOnsiteMuseumOrExhibits
chosen
Indicates that a place includes an on-site museum or exhibit area available for visitors.
-
B.
museumHolds
Indicates that a museum possesses, preserves, or has custody of a particular item or collection within its holdings.
-
C.
hasMemorialMuseum
Indicates that a memorial museum is dedicated to, associated with, or established in honor of a particular entity.
-
D.
museumAt
Indicates that an entity (such as an exhibit, artifact, or event) is located at or associated with a particular museum.
-
E.
hasMuseumType
Indicates that an entity is classified as a museum of a specific type or category.
- 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_69a8864a83848190a4ec02721306c511 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb231de14819091da3a20ed03c430 |
completed | March 7, 2026, 5:05 a.m. |
| PD | Predicate disambiguation | batch_69abafde4598819099d8229128348fd3 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.