Triple
T281075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | J |
E5354
|
entity |
| Predicate | weekdayPattern |
P3309
|
FINISHED |
| Object | supplemented by Z during rush 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: supplemented by Z during rush hours | Statement: [J, weekdayPattern, supplemented by Z during rush hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weekdayPattern Context triple: [J, weekdayPattern, supplemented by Z during rush hours]
-
A.
hasWeeklyHolyDay
Indicates that an entity observes or is associated with a recurring holy or sacred day that occurs weekly.
-
B.
isWorkHoliday
Indicates that a given day is designated as a non-working public or company holiday.
-
C.
observesDay
Indicates that an entity recognizes, commemorates, or practices a particular day (such as a holiday, event, or observance) according to some calendar or tradition.
-
D.
weekendService
Indicates that a service, operation, or activity is provided or occurs specifically on weekends.
-
E.
typicalSchedule
chosen
Indicates the usual or standard timing and sequence of activities or events associated with an entity.
- 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_69a257e6c8788190987dfe705ca2912a |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25e0a23c0819083abee28b2dea49c |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b77e028819087e606fc321219f7 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:59 a.m.