Triple
T21410603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Height of Buildings Act of 1899 |
E528156
|
entity |
| Predicate | effectOnUrbanForm |
P133158
|
FINISHED |
| Object | shaped Washington, D.C.’s low-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: shaped Washington, D.C.’s low-rise skyline | Statement: [Height of Buildings Act of 1899, effectOnUrbanForm, shaped Washington, D.C.’s low-rise skyline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnUrbanForm Context triple: [Height of Buildings Act of 1899, effectOnUrbanForm, shaped Washington, D.C.’s low-rise skyline]
-
A.
impactOnUrbanAreas
chosen
Indicates the effect or influence that something has on cities or densely populated urban environments.
-
B.
都市景観への影響
Indicates the effect or impact that something has on the appearance, structure, or overall quality of the urban landscape.
-
C.
urbanDesign
Indicates the relationship in which an entity is responsible for planning, organizing, or shaping the physical layout and functional structure of urban spaces.
-
D.
urbanMorphology
Indicates the spatial form, structure, and layout relationships that characterize the physical configuration of an urban area.
-
E.
hasUrbanDesign
Indicates that an entity possesses or is associated with a specific urban design plan, feature, or configuration.
- 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_69e0c454c248819093425d1099101c09 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b1b6595481908cdf915e3585ed08 |
completed | April 22, 2026, 11:32 a.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:42 p.m.