Triple
T38459320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heritage Plaza |
E912404
|
entity |
| Predicate | skylineCategory |
P56210
|
FINISHED |
| Object | Houston 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: Houston skyscraper | Statement: [Heritage Plaza, skylineCategory, Houston skyscraper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: skylineCategory Context triple: [Heritage Plaza, skylineCategory, Houston skyscraper]
-
A.
skylineType
Indicates the general visual or structural character of a skyline, such as its dominant form, density, or profile.
-
B.
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.
-
C.
cornerCategory
Indicates that something is classified as belonging to a specific type or category of corner.
-
D.
cityView
Indicates that one entity offers a view of, or overlooks, a city.
-
E.
urbanPlanningCategory
Indicates the classification of an area, project, or feature according to its designated role or function within an urban planning framework.
- 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_69f76e84e2dc81908badf05b3aafa9ea |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcce7afcd08190906cc3801152656a |
completed | May 7, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69fcccf140ec8190862d53388a5f40d7 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.