Triple
T27860079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meadow Lane (street) |
E704200
|
entity |
| Predicate | hasTypicalSpeedLimitCategory |
P72264
|
FINISHED |
| Object | local residential speed limit |
—
|
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 residential speed limit | Statement: [Meadow Lane (street), hasTypicalSpeedLimitCategory, local residential speed limit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalSpeedLimitCategory Context triple: [Meadow Lane (street), hasTypicalSpeedLimitCategory, local residential speed limit]
-
A.
hasSpeedLimitCategory
chosen
Indicates that an entity is associated with a specific category or classification of speed limit.
-
B.
hasSpeedLimit
Indicates that a specified maximum allowable speed is imposed on the associated entity or context.
-
C.
hasSpeedLimitCharacteristic
Indicates that an entity is associated with a specific speed limit property or constraint.
-
D.
hasNoGeneralSpeedLimit
Indicates that there is no legally enforced general maximum speed limit for travel on the relevant road or in the specified area.
-
E.
hasSpeedRestriction
Indicates that an entity is subject to a specified limit on its allowable speed.
- 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_69ef840e614c8190a88cf9638c14a265 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: April 27, 2026, 6:17 p.m.