Triple
T24592308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kancamagus Pass |
E608568
|
entity |
| Predicate | maximumSpeedLimitApprox |
P10944
|
FINISHED |
| Object | 35–45 mph |
—
|
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: 35–45 mph | Statement: [Kancamagus Pass, maximumSpeedLimitApprox, 35–45 mph]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumSpeedLimitApprox Context triple: [Kancamagus Pass, maximumSpeedLimitApprox, 35–45 mph]
-
A.
hasSpeedLimit
Indicates that a specified maximum allowable speed is imposed on the associated entity or context.
-
B.
hasSpeedLimitRange
chosen
Indicates that there is a specified minimum and maximum speed limit applicable to a given context or segment.
-
C.
speedLimitCharacteristic
Indicates that an entity has a specific speed limit property or constraint associated with it.
-
D.
typicalSpeedLimitComparedToMainline
Indicates how the typical speed limit on one road segment compares to that of the mainline or primary roadway.
-
E.
hasSpeedLimitCharacteristic
Indicates that an entity is associated with a specific speed limit property or constraint.
- 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_69e2c4cf54248190af7b0c2d9ade9830 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a9dc63208190b70f57b9821a7241 |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:30 a.m.