Triple
T32685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Encore Boston Harbor |
E651
|
entity |
| Predicate | architecturalType |
P1844
|
FINISHED |
| Object | high-rise hotel tower |
—
|
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: high-rise hotel tower | Statement: [Encore Boston Harbor, architecturalType, high-rise hotel tower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: architecturalType Context triple: [Encore Boston Harbor, architecturalType, high-rise hotel tower]
-
A.
buildingType
chosen
Indicates the specific category or function that characterizes what kind of building something is.
-
B.
architecturalStyle
Indicates the architectural design tradition, movement, or style that characterizes the form and appearance of a structure or built work.
-
C.
building
Indicates that one entity constructs, assembles, or develops another entity, typically over a period of time.
-
D.
residenceType
Indicates the kind or category of dwelling or living arrangement associated with an entity.
-
E.
significantBuilding
Indicates that a building holds notable importance, prominence, or special status within a particular context (e.g., historical, cultural, architectural, or functional).
- 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_69a2479dec388190967ba648663442c9 |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a2496ffc548190b545f998cbebd5b9 |
completed | Feb. 28, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69a248717f5081909952a8c9ed1e1742 |
completed | Feb. 28, 2026, 1:44 a.m. |
Created at: Feb. 28, 2026, 1:44 a.m.