Triple
T2772116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chatuchak Weekend Market |
E61479
|
entity |
| Predicate | openingDays |
P10069
|
FINISHED |
| Object | Saturday |
—
|
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: Saturday | Statement: [Chatuchak Weekend Market, openingDays, Saturday]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingDays Context triple: [Chatuchak Weekend Market, openingDays, Saturday]
-
A.
openingHoursCharacteristic
Indicates a relationship that specifies particular attributes or features of an entity’s opening hours, such as patterns, exceptions, or special conditions.
-
B.
daysOfOperation
chosen
Indicates the specific days on which an entity (such as a service, facility, or operation) is active or functioning.
-
C.
officialOpeningDate
Indicates the calendar date on which something is formally inaugurated or officially opened for use or operation.
-
D.
reopeningDate
Indicates the date on which something that was previously closed is opened again for use or access.
-
E.
openingWorkOf
Indicates that one work serves as the first or introductory piece in relation to another work, such as the opening item in a sequence or collection.
- 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_69ab4b7cd13481909174bca9809ed259 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abddceb9d88190961e30d521a21552 |
completed | March 7, 2026, 8:11 a.m. |
| PD | Predicate disambiguation | batch_69abdcfed608819080988e93df7bdf7c |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:57 p.m.