Triple
T4921694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rua da Prata |
E110479
|
entity |
| Predicate | hasBuildingHeightPattern |
P47446
|
FINISHED |
| Object | uniform façades |
—
|
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: uniform façades | Statement: [Rua da Prata, hasBuildingHeightPattern, uniform façades]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuildingHeightPattern Context triple: [Rua da Prata, hasBuildingHeightPattern, uniform façades]
-
A.
hasBuildingHeightType
Indicates the classification or type used to characterize the height of a building in the relationship.
-
B.
hasBuildingPattern
chosen
Indicates that an entity exhibits or follows a particular architectural or structural building pattern.
-
C.
hasTowerHeight
Indicates that an entity (such as a tower or structure) has a specific height value associated with it.
-
D.
buildingHeightCharacteristic
Indicates the specific height-related property or measurement that characterizes a building.
-
E.
buildingHeightContext
Indicates the contextual or situational factors under which a building’s height is defined, measured, or interpreted.
- 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_69bd4413f9908190afcff44d7929cc4c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ffc2ab08190992db2400562bcee |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3421588190ab08e92b9558042e |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:30 p.m.