Triple
T25391742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | One Financial Center |
E636184
|
entity |
| Predicate | roofHeightRankInBoston |
P27607
|
FINISHED |
| Object | among top 20 |
—
|
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: among top 20 | Statement: [One Financial Center, roofHeightRankInBoston, among top 20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roofHeightRankInBoston Context triple: [One Financial Center, roofHeightRankInBoston, among top 20]
-
A.
rankInCityByHeight
chosen
Indicates the relative ordering of entities within a specific city based on their height, such as which is tallest, second tallest, and so on.
-
B.
buildingHeight
Indicates the vertical extent or height measurement of a building.
-
C.
buildingHeightContext
Indicates the contextual or situational factors under which a building’s height is defined, measured, or interpreted.
-
D.
rankAmongTallestBuildings
Indicates that one building is among the tallest buildings within a specified group, area, or category.
-
E.
roofHeight
Indicates the vertical distance or elevation of a roof relative to a reference level or structure.
- 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_69e75db263888190b77fff9e2827b9a2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f565719b788190bece84e6c21ebd38 |
completed | May 2, 2026, 2:46 a.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:49 p.m.