Triple
T22261810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hollis Hills |
E550243
|
entity |
| Predicate | buildingHeightProfile |
P30757
|
FINISHED |
| Object | low-rise 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: low-rise buildings | Statement: [Hollis Hills, buildingHeightProfile, low-rise buildings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildingHeightProfile Context triple: [Hollis Hills, buildingHeightProfile, low-rise buildings]
-
A.
buildingHeight
Indicates the vertical extent or height measurement of a building.
-
B.
buildingHeightContext
chosen
Indicates the contextual or situational factors under which a building’s height is defined, measured, or interpreted.
-
C.
buildingHeightCharacteristic
Indicates the specific height-related property or measurement that characterizes a building.
-
D.
rankInCityByHeight
Indicates the relative ordering of entities within a specific city based on their height, such as which is tallest, second tallest, and so on.
-
E.
approximateHeightOfTallestStructure
Indicates the estimated height value associated with the tallest structure in a given context or set.
- 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_69e11e42adb8819087714772ea606709 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f141b87de0819088b7553406343068 |
completed | April 28, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69e72fe1e0cc8190bd13cff2a0846225 |
completed | April 21, 2026, 8:05 a.m. |
Created at: April 16, 2026, 8:39 p.m.