Triple
T28827973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blok M |
E727963
|
entity |
| Predicate | hasTypicalOpeningHoursPattern |
P17011
|
FINISHED |
| Object | late-night operations for many venues |
—
|
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: late-night operations for many venues | Statement: [Blok M, hasTypicalOpeningHoursPattern, late-night operations for many venues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalOpeningHoursPattern Context triple: [Blok M, hasTypicalOpeningHoursPattern, late-night operations for many venues]
-
A.
openingHoursCharacteristic
chosen
Indicates a relationship that specifies particular attributes or features of an entity’s opening hours, such as patterns, exceptions, or special conditions.
-
B.
has24HourOperations
Indicates that an entity operates continuously for 24 hours a day without closing.
-
C.
plannedOpeningPeriod
Indicates the time span during which something is scheduled or intended to open or begin operating.
-
D.
hoursOfOperation
Indicates the time periods during which a place or service is open and available for use.
-
E.
openingTime
Indicates the time at which a place, service, or event begins operating or becomes accessible.
- 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: April 28, 2026, 6:36 a.m.