Triple
T36443001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jalan Bukit Bintang |
E897788
|
entity |
| Predicate | pedestrianZoneFeatures |
P144145
|
FINISHED |
| Object | wide sidewalks |
—
|
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: wide sidewalks | Statement: [Jalan Bukit Bintang, pedestrianZoneFeatures, wide sidewalks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pedestrianZoneFeatures Context triple: [Jalan Bukit Bintang, pedestrianZoneFeatures, wide sidewalks]
-
A.
pedestrianFeatures
chosen
Indicates the presence, type, or characteristics of infrastructure or design elements intended for pedestrian use or safety.
-
B.
pedestrianizedAreas
Indicates areas where vehicle traffic is restricted or removed so that pedestrians have priority use of the space.
-
C.
pedestrianFriendly
Indicates that an environment, route, or area is designed or suitable for safe, comfortable, and convenient use by pedestrians.
-
D.
hasPedestrianPlazaOn
Indicates that a pedestrian plaza is located on, or directly associated with, a specified surface, structure, or area.
-
E.
pedestrianActivity
Indicates that an entity is engaged in or associated with walking or other on-foot movement or behavior.
- 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_69f76e5720b481908f8177ac24a7560b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.