Triple
T7746230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bank of California Building (Seattle) |
E175636
|
entity |
| Predicate | hasFloorsAboveGround |
P78480
|
FINISHED |
| Object | high-rise |
—
|
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 | Statement: [Bank of California Building (Seattle), hasFloorsAboveGround, high-rise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFloorsAboveGround Context triple: [Bank of California Building (Seattle), hasFloorsAboveGround, high-rise]
-
A.
hasGroundFloor
Indicates that a building or structure includes a ground-level floor as part of its layout or design.
-
B.
hasUpperFloor
Indicates that one entity possesses or includes an upper floor relative to another level or reference point.
-
C.
hasGroundFloorUse
Indicates that a building or structure is associated with a specific functional use assigned to its ground floor level.
-
D.
hasUpperFloorUse
Indicates that an entity’s upper floor is assigned or designated for a particular use or function.
-
E.
numberOfFloors
Indicates the total count of distinct floor levels that a building or structure has.
- F. None of above. chosen
Provenance (4 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_69c69960b3588190a53aa590d31d9544 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70402169481909b219dc5f4a64b9b |
completed | March 27, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69c7016c4a748190a7012030edaefcee |
completed | March 27, 2026, 10:15 p.m. |
| PDg | Predicate description generation | batch_69c7040091608190a9e46ecfb2ff0bca |
completed | March 27, 2026, 10:26 p.m. |
Created at: March 27, 2026, 4:08 p.m.