Triple
T10351332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Summit One Vanderbilt |
E243887
|
entity |
| Predicate | heightContext |
P93816
|
FINISHED |
| Object | near the top of One Vanderbilt skyscraper |
—
|
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: near the top of One Vanderbilt skyscraper | Statement: [Summit One Vanderbilt, heightContext, near the top of One Vanderbilt skyscraper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heightContext Context triple: [Summit One Vanderbilt, heightContext, near the top of One Vanderbilt skyscraper]
-
A.
hasHeight
Indicates that one entity possesses a specific vertical measurement or stature.
-
B.
heightClass
Indicates the categorical height level or range to which an entity is assigned (e.g., short, medium, tall).
-
C.
heightReference
Indicates that one entity’s height is being measured, compared, or defined relative to another specified reference point or standard.
-
D.
heightDescription
Indicates how tall an entity is, typically expressed in descriptive or qualitative terms rather than a precise measurement.
-
E.
structureHeight
Indicates that a structure has a specific vertical measurement or height.
- 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_69d381b22b8c8190aaed476be5f872a9 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9489f9481908fc1c818e81c1cc2 |
completed | April 7, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69d4dfa657f481909cc5cc8fec00ad19 |
completed | April 7, 2026, 10:42 a.m. |
| PDg | Predicate description generation | batch_69d4e91ce2008190af252c140370b7f2 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, 11:57 a.m.