Triple
T7068904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Denali Park Road |
E164631
|
entity |
| Predicate | vehicleRestrictionMile |
P74823
|
FINISHED |
| Object | around Mile 15 |
—
|
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: around Mile 15 | Statement: [Denali Park Road, vehicleRestrictionMile, around Mile 15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vehicleRestrictionMile Context triple: [Denali Park Road, vehicleRestrictionMile, around Mile 15]
-
A.
mileageAccrual
Indicates the accumulation or earning of mileage (such as distance-based points or credits) as a result of certain actions or usage.
-
B.
vehiclePolicy
Indicates a relationship where a policy governs, regulates, or defines rules and conditions for the use, operation, or management of a vehicle.
-
C.
distanceTraveled
Indicates the total length of the path an entity has moved over a period of time or between two points.
-
D.
hasLimitedRoadAccess
Indicates that an entity can only be reached by a small number of roads, restricted routes, or otherwise constrained vehicular access.
-
E.
vehicleUsed
Indicates that a particular vehicle is utilized or employed in performing an action, event, or activity.
- F. None of above. chosen
Provenance (4 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_69c6887b96548190a8a9b3ac8adf4119 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e4a935488190a8c9c21bf30dd5d4 |
completed | March 27, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bfcb948190a5ada74fb8c054cb |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e4a15b088190bee9a23e94aaac53 |
completed | March 27, 2026, 8:12 p.m. |
Created at: March 27, 2026, 2:39 p.m.