Triple
T35055732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Don Valley Parkway |
E1011456
|
entity |
| Predicate | speedEnforcedBy |
P124968
|
FINISHED |
| Object | Toronto Police Service |
—
|
NE NERFINISHED |
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: Toronto Police Service | Statement: [Don Valley Parkway, speedEnforcedBy, Toronto Police Service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speedEnforcedBy Context triple: [Don Valley Parkway, speedEnforcedBy, Toronto Police Service]
-
A.
speedSupervision
chosen
Indicates a relationship where an entity monitors, controls, or enforces limits on the speed of another entity or process.
-
B.
speedLimitCharacteristic
Indicates that an entity has a specific speed limit property or constraint associated with it.
-
C.
regulatesSpeedLimitBy
Indicates that one entity determines, controls, or sets the speed limit applicable to another entity or context.
-
D.
governingSpeedRange
Indicates the range of speeds within which a governing or limiting mechanism is intended to operate or apply.
-
E.
hasSpeedLimit
Indicates that a specified maximum allowable speed is imposed on the associated entity or context.
- 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_69f76dd09c308190a523454853ce842b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f785d09b60819081c33c23d857ea75 |
completed | May 3, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.