Triple
T31586134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keong Saik Road shophouses |
E805960
|
entity |
| Predicate | streetscapeQuality |
P24448
|
FINISHED |
| Object | human-scale |
—
|
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: human-scale | Statement: [Keong Saik Road shophouses, streetscapeQuality, human-scale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streetscapeQuality Context triple: [Keong Saik Road shophouses, streetscapeQuality, human-scale]
-
A.
streetscapeStyle
Indicates the characteristic visual and design style that defines the overall appearance and layout of a street and its surrounding public realm.
-
B.
isPartOfStreetscape
Indicates that something forms a component or element within the overall layout or visual composition of a streetscape.
-
C.
hasStreetEnvironment
chosen
Indicates that an entity is associated with or characterized by a particular type or quality of street-level surroundings or conditions.
-
D.
urbanLandscapeCharacterizedBy
Indicates that an urban landscape possesses or is defined by specific distinguishing features, qualities, or elements.
-
E.
cityScene
Indicates a scene or setting that takes place within an urban or city environment.
- 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 10:25 p.m.