Triple
T33581550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Business routes of U.S. Route 19 |
E860161
|
entity |
| Predicate | typicalSpeedLimitComparedToParent |
P106467
|
FINISHED |
| Object | lower |
—
|
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: lower | Statement: [Business routes of U.S. Route 19, typicalSpeedLimitComparedToParent, lower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSpeedLimitComparedToParent Context triple: [Business routes of U.S. Route 19, typicalSpeedLimitComparedToParent, lower]
-
A.
typicalSpeedLimitComparedToMainline
chosen
Indicates how the typical speed limit on one road segment compares to that of the mainline or primary roadway.
-
B.
previousSpeedLimit
Indicates that a specified speed limit was in effect immediately before the current or another referenced speed limit.
-
C.
hasSpeedLimit
Indicates that a specified maximum allowable speed is imposed on the associated entity or context.
-
D.
regulatesSpeedLimitBy
Indicates that one entity determines, controls, or sets the speed limit applicable to another entity or context.
-
E.
hasSpeedLimitRange
Indicates that there is a specified minimum and maximum speed limit applicable to a given context or segment.
- 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_69f3497d37848190afcbb5ef3f5c7376 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:40 a.m.