Triple
T33438524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Tower, New York City |
E856292
|
entity |
| Predicate | hasElevatedViews |
P126122
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Blue Tower, New York City, hasElevatedViews, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElevatedViews Context triple: [Blue Tower, New York City, hasElevatedViews, yes]
-
A.
hasElevatedSections
Indicates that one entity contains or features parts that are raised or elevated relative to its other sections.
-
B.
hasExpansiveViews
chosen
Indicates that an entity offers wide-ranging, unobstructed, or panoramic views of its surroundings.
-
C.
hasViewThrough
Indicates that one entity can be seen or visually perceived through another entity acting as an intermediate medium or opening.
-
D.
hasElevatedBranch
Indicates that one entity possesses or features a branch that is positioned higher or raised relative to a reference level or structure.
-
E.
isElevatedAbove
Indicates that one entity is positioned at a higher vertical level or altitude than another entity.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 1, 2026, 1:36 a.m.