Triple
T3556910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CTA Brown Line |
E75239
|
entity |
| Predicate | rushHourPattern |
P26031
|
FINISHED |
| Object | increased frequency during peak periods |
—
|
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: increased frequency during peak periods | Statement: [CTA Brown Line, rushHourPattern, increased frequency during peak periods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rushHourPattern Context triple: [CTA Brown Line, rushHourPattern, increased frequency during peak periods]
-
A.
rushHourServicePattern
chosen
Indicates that a service operates according to a specific pattern or schedule that applies only during rush-hour or peak travel times.
-
B.
populationPeakPeriod
Indicates the time period during which a population reached its highest recorded level.
-
C.
budTime
Indicates the time or period when a bud forms or begins to develop.
-
D.
offPeakServicePattern
Indicates the service pattern or schedule that applies during off-peak (non-rush-hour) times.
-
E.
typicalTimes
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_69ad85d45090819086f34fb85d850a1e |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc057cc788190a6c4f3781f43abce |
completed | March 8, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69adb83270ac819083967db0570167d2 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:20 p.m.