Triple
T34393529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HSBC Rain Vortex |
E882769
|
entity |
| Predicate | dailyOperatingHours |
P10068
|
FINISHED |
| Object | approximately 07:30–00:30 |
—
|
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: approximately 07:30–00:30 | Statement: [HSBC Rain Vortex, dailyOperatingHours, approximately 07:30–00:30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dailyOperatingHours Context triple: [HSBC Rain Vortex, dailyOperatingHours, approximately 07:30–00:30]
-
A.
hoursOfOperation
chosen
Indicates the time periods during which a place or service is open and available for use.
-
B.
openingHoursCharacteristic
Indicates a relationship that specifies particular attributes or features of an entity’s opening hours, such as patterns, exceptions, or special conditions.
-
C.
daysOfOperation
Indicates the specific days on which an entity (such as a service, facility, or operation) is active or functioning.
-
D.
openingTime
Indicates the time at which a place, service, or event begins operating or becomes accessible.
-
E.
has24HourOperations
Indicates that an entity operates continuously for 24 hours a day without closing.
- 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_69f349c1304081909331872829e38106 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:59 a.m.