Triple
T130266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sever Hall |
E2638
|
entity |
| Predicate | hasArchitecturalType |
P607
|
FINISHED |
| Object | Romanesque academic building |
—
|
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: Romanesque academic building | Statement: [Sever Hall, hasArchitecturalType, Romanesque academic building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArchitecturalType Context triple: [Sever Hall, hasArchitecturalType, Romanesque academic building]
-
A.
architectureType
Indicates the specific style or category of architecture that characterizes or defines an entity.
-
B.
architecturalStyle
chosen
Indicates the architectural design tradition, movement, or style that characterizes the form and appearance of a structure or built work.
-
C.
hasBuildingHeightType
Indicates the classification or type used to characterize the height of a building in the relationship.
-
D.
hasStructureType
Indicates that an entity possesses or is classified by a specific structural type or configuration.
-
E.
hasInfrastructureType
Indicates that an entity possesses or is associated with a specific category or type of infrastructure.
- 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_69a2520c0f3481908b0ed054a2fca8d0 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a257845c548190bfb49409988d1c57 |
completed | Feb. 28, 2026, 2:48 a.m. |
| PD | Predicate disambiguation | batch_69a2564da96c8190aa8204de25229c15 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:30 a.m.