Triple
T21697832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Z train serves during rush hours in peak direction |
E535571
|
entity |
| Predicate | weekdayOperation |
P19611
|
FINISHED |
| Object | weekdays |
—
|
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: weekdays | Statement: [Z train serves during rush hours in peak direction, weekdayOperation, weekdays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weekdayOperation Context triple: [Z train serves during rush hours in peak direction, weekdayOperation, weekdays]
-
A.
weekdayServicePattern
chosen
Indicates a service pattern or schedule that specifically applies on weekdays rather than weekends or holidays.
-
B.
dayType
Indicates the classification or category of a given day based on its characteristics or role (e.g., weekday, weekend, holiday).
-
C.
dayPattern
Indicates the recurring schedule or configuration of days on which an event, action, or condition occurs.
-
D.
dayUse
Indicates that something is intended or permitted to be used during the daytime.
-
E.
operatesDaytime
Indicates that an entity performs its primary function or activity during daytime hours.
- 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_69e0c46a6ee481908836e1420fb78c9b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef9b7caca0819083d839b276ae015b |
completed | April 27, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69e6969113cc8190ab69855ef5667e4b |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:45 p.m.