Triple
T32408185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Reading skyline |
E828137
|
entity |
| Predicate | hasHeightProfile |
P50562
|
FINISHED |
| Object | predominantly mid‑rise |
—
|
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: predominantly mid‑rise | Statement: [City of Reading skyline, hasHeightProfile, predominantly mid‑rise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeightProfile Context triple: [City of Reading skyline, hasHeightProfile, predominantly mid‑rise]
-
A.
altitudeProfile
Indicates the variation of elevation or height along a path, route, or trajectory over distance or time.
-
B.
hasAltitudeFeature
Indicates that an entity possesses a characteristic or attribute related to its elevation or vertical position above a reference level.
-
C.
hasElevationFeature
chosen
Indicates that one entity possesses or is characterized by a particular elevation-related feature or attribute, such as height, altitude, or vertical relief.
-
D.
hasTopElevation
Indicates that an entity has a specified maximum or highest elevation value.
-
E.
hasAltitudeDifference
Indicates that there is a specific vertical height difference between two entities or locations.
- 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_69f34919f300819092b541c6277cd68a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: May 1, 2026, 12:53 a.m.