Triple
T11442696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jonker Street |
E271182
|
entity |
| Predicate | pedestrianizedDuring |
P99319
|
FINISHED |
| Object | night market hours |
—
|
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: night market hours | Statement: [Jonker Street, pedestrianizedDuring, night market hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pedestrianizedDuring Context triple: [Jonker Street, pedestrianizedDuring, night market hours]
-
A.
pedestrianizedSince
Indicates that an area or street has been designated for pedestrian use only starting from a specific point in time.
-
B.
pedestrianOnly
Indicates that a path, area, or route is designated exclusively for pedestrians and prohibits vehicle access.
-
C.
pedestrianFriendly
Indicates that an environment, route, or area is designed or suitable for safe, comfortable, and convenient use by pedestrians.
-
D.
pedestrianActivity
Indicates that an entity is engaged in or associated with walking or other on-foot movement or behavior.
-
E.
hasPedestrianPlazaOn
Indicates that a pedestrian plaza is located on, or directly associated with, a specified surface, structure, or area.
- F. None of above. chosen
Provenance (4 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_69d6aadff8888190a13f253f0d460874 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d808891b7481908bf5a80cb7644061 |
completed | April 9, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69d7e7162b288190a0bfb89f7eb747c7 |
completed | April 9, 2026, 5:51 p.m. |
| PDg | Predicate description generation | batch_69d800115af08190bba53dd3ff561ca1 |
completed | April 9, 2026, 7:37 p.m. |
Created at: April 8, 2026, 9:35 p.m.