Triple
T2672634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgetown Historic District |
E55780
|
entity |
| Predicate | buildingHeight |
P41605
|
FINISHED |
| Object | predominantly low-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 low-rise | Statement: [Georgetown Historic District, buildingHeight, predominantly low-rise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildingHeight Context triple: [Georgetown Historic District, buildingHeight, predominantly low-rise]
-
A.
buildingHeightContext
Indicates the contextual or situational factors under which a building’s height is defined, measured, or interpreted.
-
B.
tallestBuildingIn
Indicates that one entity is the tallest building located within the area or region specified by the other entity.
-
C.
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.
-
D.
towerName
Indicates the specific name assigned to a tower in the relationship.
-
E.
towerLocation
Indicates that a tower is located at, or associated with, a specific place or geographic location.
- 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_69ab49e54de48190be708cd1cf8be073 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd98f98908190b5c6fb38d3d4367a |
completed | March 7, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69abd8190ad481908f3e14ac84d0940a |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd8f98c348190a68064c565589459 |
completed | March 7, 2026, 7:51 a.m. |
Created at: March 6, 2026, 9:54 p.m.