Triple
T94093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of Havana |
E1890
|
entity |
| Predicate | hasMainBuildingStyle |
P607
|
FINISHED |
| Object | neoclassical architecture |
—
|
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: neoclassical architecture | Statement: [University of Havana, hasMainBuildingStyle, neoclassical architecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainBuildingStyle Context triple: [University of Havana, hasMainBuildingStyle, neoclassical architecture]
-
A.
architecturalStyle
chosen
Indicates the architectural design tradition, movement, or style that characterizes the form and appearance of a structure or built work.
-
B.
buildingType
Indicates the specific category or function that characterizes what kind of building something is.
-
C.
architectOfMainBuilding
Indicates that one entity is the architect who designed the main building associated with another entity.
-
D.
significantBuilding
Indicates that a building holds notable importance, prominence, or special status within a particular context (e.g., historical, cultural, architectural, or functional).
-
E.
hasBuildingHeightType
Indicates the classification or type used to characterize the height of a building in the relationship.
- 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_69a24d4862f881908cc8b89d3a78031d |
completed | Feb. 28, 2026, 2:04 a.m. |
| NER | Named-entity recognition | batch_69a2512ef600819084d3c627f0d534f4 |
completed | Feb. 28, 2026, 2:21 a.m. |
| PD | Predicate disambiguation | batch_69a24eb9a5ac8190b1d1300e8c4e3606 |
completed | Feb. 28, 2026, 2:11 a.m. |
Created at: Feb. 28, 2026, 2:09 a.m.