Triple
T26535660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 10 Hudson Yards |
E671236
|
entity |
| Predicate | isOneOfFirstTowersOf |
P165045
|
FINISHED |
| Object | Hudson Yards Redevelopment Project |
—
|
NE NERFINISHED |
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: Hudson Yards Redevelopment Project | Statement: [10 Hudson Yards, isOneOfFirstTowersOf, Hudson Yards Redevelopment Project]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOneOfFirstTowersOf Context triple: [10 Hudson Yards, isOneOfFirstTowersOf, Hudson Yards Redevelopment Project]
-
A.
hasTower
Indicates that one entity possesses, contains, or is characterized by the presence of a tower.
-
B.
isObservationTower
Indicates that something functions as an observation tower, serving primarily as a structure for viewing or monitoring an area from an elevated position.
-
C.
towersOver
Indicates that one entity is significantly taller or higher in position than another, often in a way that appears dominant or imposing.
-
D.
hasTowerPosition
Indicates that an entity occupies or is assigned a specific position or location within a tower.
-
E.
isTallestTowerIn
Indicates that one tower is the tallest tower within a specified location or set of towers.
- 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_69eeb3206e748190b90c85cc81f38c91 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 27, 2026, 1:38 a.m.