Triple
T1143125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aalsmeer flower market stalls (part of Bloemenmarkt) |
E23499
|
entity |
| Predicate | typicalOpeningTime |
P6833
|
FINISHED |
| Object | daytime hours |
—
|
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: daytime hours | Statement: [Aalsmeer flower market stalls (part of Bloemenmarkt), typicalOpeningTime, daytime hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalOpeningTime Context triple: [Aalsmeer flower market stalls (part of Bloemenmarkt), typicalOpeningTime, daytime hours]
-
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.
typicalBusinessHourStartLocalTime
Indicates the local time at which a business’s normal operating hours typically begin.
-
C.
roofOpeningTime
Indicates the time at which a roof (typically movable or retractable) is opened.
-
D.
hoursOfOperation
Indicates the time periods during which a place or service is open and available for use.
-
E.
typicalTimes
chosen
Indicates the usual or characteristic times at which an event, activity, or condition typically occurs.
- 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_69a493ef399c8190b04b9146d2314f59 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bc4e93d48190b9fea886bf61aad7 |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4d4104819084027a043c6118cb |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.