Triple
T27896695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Havana City Hall |
E705511
|
entity |
| Predicate | hostBuildingCurrentUse |
P77240
|
FINISHED |
| Object | Museum of the City of Havana |
—
|
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: Museum of the City of Havana | Statement: [Havana City Hall, hostBuildingCurrentUse, Museum of the City of Havana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostBuildingCurrentUse Context triple: [Havana City Hall, hostBuildingCurrentUse, Museum of the City of Havana]
-
A.
currentBuildingUse
Indicates the present functional purpose or activity for which a building is being used.
-
B.
hostBuilding
chosen
Indicates that one entity serves as the building or physical structure that houses, contains, or accommodates another entity.
-
C.
hostsBuilding
Indicates that one entity serves as the location or site that accommodates or contains a particular building.
-
D.
buildingUsedBy
Indicates that a particular building is utilized or occupied by a specified entity for some purpose.
-
E.
currentBuilding
Indicates that an entity is located in, associated with, or belongs to the building that is relevant in the current context.
- 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_69ef96b490ac8190a412d04c5d009f3e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f639f4c7c88190ad20ec170606d707 |
completed | May 2, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69f6318be69481909d1bcf29b7b60eb2 |
completed | May 2, 2026, 5:17 p.m. |
Created at: April 27, 2026, 6:39 p.m.