Triple
T35649135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harrison Road (Selah area) |
E1030092
|
entity |
| Predicate | typicalSpeedCategory |
P9902
|
FINISHED |
| Object | local street speed limits |
—
|
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: local street speed limits | Statement: [Harrison Road (Selah area), typicalSpeedCategory, local street speed limits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSpeedCategory Context triple: [Harrison Road (Selah area), typicalSpeedCategory, local street speed limits]
-
A.
recordSpeedCategory
Indicates the classification of an entity’s speed into a predefined category (e.g., slow, normal, fast) based on its recorded speed.
-
B.
typicalSpeedEnvironment
Indicates that an environment is characterized by a particular speed that is typical or normal for it.
-
C.
speedClass
chosen
Indicates the categorical speed level or range assigned to an entity based on how fast it moves or operates.
-
D.
typicalTopSpeedRange
Indicates the usual range of maximum speeds that an entity is capable of under normal conditions.
-
E.
relativeSpeedCategory
Indicates the categorized comparison of one entity’s speed relative to another (e.g., slower, similar, or faster).
- 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_69f76e0938088190a8f199631e97dec3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.