Triple
T35028452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sino Centre |
E1010406
|
entity |
| Predicate | openingHoursTypical |
P6833
|
FINISHED |
| Object | around 11:00–23:00 |
—
|
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: around 11:00–23:00 | Statement: [Sino Centre, openingHoursTypical, around 11:00–23:00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingHoursTypical Context triple: [Sino Centre, openingHoursTypical, around 11:00–23:00]
-
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.
openingTime
Indicates the time at which a place, service, or event begins operating or becomes accessible.
-
C.
typicalTimes
chosen
Indicates the usual or characteristic times at which an event, activity, or condition typically occurs.
-
D.
hoursOfOperation
Indicates the time periods during which a place or service is open and available for use.
-
E.
plannedOpeningPeriod
Indicates the time span during which something is scheduled or intended to open or begin operating.
- 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_69f76dccf0108190af43b465d3750196 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:01 p.m.