Triple
T13569613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harbor of the Future 21 |
E324122
|
entity |
| Predicate | skylineType |
P110109
|
FINISHED |
| Object | modern high-rise skyline |
—
|
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: modern high-rise skyline | Statement: [Harbor of the Future 21, skylineType, modern high-rise skyline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: skylineType Context triple: [Harbor of the Future 21, skylineType, modern high-rise skyline]
-
A.
partOfSkylineOf
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.
-
B.
ridgeType
Indicates the specific morphological or structural category that a ridge belongs to within a classification of ridge forms.
-
C.
sightType
Indicates the specific kind or category of sight or visual perception associated with an entity or event.
-
D.
towerType
Indicates the specific kind or classification of a tower that an entity is associated with or represents.
-
E.
isSkyscraperIn
Indicates that a skyscraper is located within or belongs to a specified geographic area or place.
- 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_69d8076830b48190910a902bae5888e2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb00f5b8881908617f42d227ed137 |
completed | April 12, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_69dbae161a0481909f9d3f40ca4e0ac5 |
completed | April 12, 2026, 2:37 p.m. |
| PDg | Predicate description generation | batch_69dbaf7fefa881908471f1400f813ccc |
completed | April 12, 2026, 2:43 p.m. |
Created at: April 9, 2026, 9:48 p.m.