Triple
T14544825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waterworks Road retail strip |
E341262
|
entity |
| Predicate | typicalBuildingForm |
P44411
|
FINISHED |
| Object | street-front shops |
—
|
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: street-front shops | Statement: [Waterworks Road retail strip, typicalBuildingForm, street-front shops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBuildingForm Context triple: [Waterworks Road retail strip, typicalBuildingForm, street-front shops]
-
A.
buildingType
Indicates the specific category or function that characterizes what kind of building something is.
-
B.
architectureType
Indicates the specific style or category of architecture that characterizes or defines an entity.
-
C.
buildingShape
Indicates the geometric form or outline that characterizes a building’s overall structure.
-
D.
originalBuildingType
Indicates the type or category of building that something was initially constructed or designated to be, before any later changes or repurposing.
-
E.
hasBuildingForm
chosen
Indicates that an entity possesses or is characterized by a particular architectural or structural building form.
- 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_69d822db9c8481908213ceb39585f792 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb1bfc2b48190adb0897682c26a9a |
completed | April 14, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69de5c546c7081909e27d504ec360c5c |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:22 a.m.