Triple
T20263703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Westpark Tollway |
E498908
|
entity |
| Predicate | peakTraffic |
P4588
|
FINISHED |
| Object | weekday 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: weekday rush hours | Statement: [Westpark Tollway, peakTraffic, weekday rush hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakTraffic Context triple: [Westpark Tollway, peakTraffic, weekday rush hours]
-
A.
roadTraffic
Indicates the presence, flow, or conditions of vehicles and movement along roads or streets.
-
B.
trafficLevel
chosen
Indicates the degree of congestion or flow intensity present in a transportation network or route at a given time.
-
C.
trafficDirection
Indicates the direction in which traffic is intended or allowed to move relative to a given reference point or segment.
-
D.
touristTraffic
Indicates the level, flow, or intensity of tourists visiting or moving through a particular place or area.
-
E.
hasCommuterTraffic
Indicates that there is regular, recurring traffic flow associated with people traveling between their homes and places of work or study.
- 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_69da6275fa6c8190952924930adee150 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e674ccff008190920b418f51dc4311 |
completed | April 20, 2026, 6:47 p.m. |
| PD | Predicate disambiguation | batch_69e55b1e5e1c8190ba8a5544b1db9e1d |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:41 p.m.