Triple
T12585444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solow Building |
E300443
|
entity |
| Predicate | isSkyscraperType |
P7154
|
FINISHED |
| Object | commercial office 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: commercial office tower | Statement: [Solow Building, isSkyscraperType, commercial office tower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSkyscraperType Context triple: [Solow Building, isSkyscraperType, commercial office tower]
-
A.
isSkyscraperIn
Indicates that a skyscraper is located within or belongs to a specified geographic area or place.
-
B.
wasTallestBuildingOfType
Indicates that a building held the status of being the tallest among all buildings of a specified type (e.g., category, function, or classification) during a given context or time period.
-
C.
hasBuildingHeightType
Indicates the classification or type used to characterize the height of a building in the relationship.
-
D.
towerType
chosen
Indicates the specific kind or classification of a tower that an entity is associated with or represents.
-
E.
locatedInSkyscraper
Indicates that one entity is physically situated within or inside a skyscraper.
- 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_69d7bde87b648190bcd0266e9efde098 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954e6e20481908bca684c4b497c48 |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95416cbd88190b2c65196162349bc |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 5:04 p.m.