Triple
T7074893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 34th Street–Hudson Yards |
E164790
|
entity |
| Predicate | depthBelowStreet |
P16571
|
FINISHED |
| Object | approximately 125 feet |
—
|
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: approximately 125 feet | Statement: [34th Street–Hudson Yards, depthBelowStreet, approximately 125 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depthBelowStreet Context triple: [34th Street–Hudson Yards, depthBelowStreet, approximately 125 feet]
-
A.
hasUndergroundDepth
Indicates that one entity has a specified vertical extent or depth located below the ground surface relative to another reference or context.
-
B.
numberOfBasementLevels
Indicates the total count of basement levels associated with a given structure or property.
-
C.
elevationBelowGround
Indicates that one entity’s elevation is located beneath the ground surface or reference ground level.
-
D.
hasStreetLevel
Indicates that something is located at, accessible from, or directly associated with the street level of a building or area.
-
E.
depthFeetApprox
chosen
Indicates an approximate measurement of an entity’s depth expressed in feet.
- 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_69c6887cbc6c8190bdfac42d940f4d8a |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e4ce3d3c81908cbb912b256aadbf |
completed | March 27, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bfcb948190a5ada74fb8c054cb |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:40 p.m.