Triple
T9547707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hang Dao Street |
E230335
|
entity |
| Predicate | nightMarketFrequency |
P32815
|
FINISHED |
| Object | regularly on weekends |
—
|
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: regularly on weekends | Statement: [Hang Dao Street, nightMarketFrequency, regularly on weekends]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nightMarketFrequency Context triple: [Hang Dao Street, nightMarketFrequency, regularly on weekends]
-
A.
nightlifePattern
Indicates a recurring way entities engage in or are associated with nightlife activities, such as typical behaviors, schedules, or participation patterns during night hours.
-
B.
marketFrequency
chosen
Indicates how often a particular market-related event, activity, or transaction occurs within a given time period.
-
C.
nightServicePattern
Indicates that a service or operation follows a specific pattern or schedule that applies only during nighttime hours.
-
D.
nightService
Indicates that a service operates or is available during nighttime hours.
-
E.
marketHeldOn
Indicates that a market event takes place at a specific time and/or location.
- 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_69ca847c70b8819088a0a0bad64a50d6 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9904732c8190ab60ecc47c995cbe |
completed | April 1, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69ccd58bd21881908b860e3ee469af13 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:02 p.m.