Triple
T16334961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Downtown Norfolk |
E396652
|
entity |
| Predicate | hasSkyline |
P56210
|
FINISHED |
| Object | high-rise office buildings |
—
|
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: high-rise office buildings | Statement: [Downtown Norfolk, hasSkyline, high-rise office buildings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSkyline Context triple: [Downtown Norfolk, hasSkyline, high-rise office buildings]
-
A.
hasSkyway
Indicates that there is an elevated, usually enclosed walkway or bridge connecting two or more structures or areas.
-
B.
skylineType
Indicates the general visual or structural character of a skyline, such as its dominant form, density, or profile.
-
C.
hasSkyBar
Indicates that an establishment features a bar located on its rooftop or at a high elevation with views of the surrounding area.
-
D.
partOfSkylineOf
chosen
Indicates that one entity is a visible component or feature contributing to the overall skyline profile of another entity, typically a city or urban area.
-
E.
hasSkyLobby
Indicates that a building includes a sky lobby, a shared floor located above ground level that serves as a transfer or common area for occupants.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2c4e29db88190936a07deb5b1c1e3 |
completed | April 17, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.