Triple
T27656177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brooklyn-Queens Expressway triple cantilever structure |
E696997
|
entity |
| Predicate | hasViewFromTop |
P854
|
FINISHED |
| Object | Brooklyn Heights Promenade |
—
|
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: Brooklyn Heights Promenade | Statement: [Brooklyn-Queens Expressway triple cantilever structure, hasViewFromTop, Brooklyn Heights Promenade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasViewFromTop Context triple: [Brooklyn-Queens Expressway triple cantilever structure, hasViewFromTop, Brooklyn Heights Promenade]
-
A.
hasView
chosen
Indicates that one entity provides a visual perspective or outlook onto another entity or scene.
-
B.
hasTopScreenSize
Indicates that an entity (typically a device) possesses a top screen with a specified size or dimension.
-
C.
hasViewThrough
Indicates that one entity can be seen or visually perceived through another entity acting as an intermediate medium or opening.
-
D.
hasActivityAtTop
Indicates that an entity has an activity occurring at or associated with its topmost part or uppermost position.
-
E.
hasViewFromRooftop
Indicates that an entity provides or features a view observable from its rooftop.
- 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_69ef590abd3c8190834d0193bde12007 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 27, 2026, 2:34 p.m.