Triple
T31807143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US 250 Bus. |
E811902
|
entity |
| Predicate | speedProfile |
P172916
|
FINISHED |
| Object | lower speed limits than U.S. Route 250 mainline |
—
|
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 speed limits than U.S. Route 250 mainline | Statement: [US 250 Bus., speedProfile, lower speed limits than U.S. Route 250 mainline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speedProfile Context triple: [US 250 Bus., speedProfile, lower speed limits than U.S. Route 250 mainline]
-
A.
speedAchieved
Indicates that a particular speed has been reached or attained by an entity during an event or action.
-
B.
speed
Indicates the rate at which an entity moves or changes position over time.
-
C.
plannedSpeed
Indicates the intended or target speed that an entity is expected or scheduled to maintain, rather than its actual current speed.
-
D.
speedDependsOn
Indicates that the speed of one entity is determined or influenced by another specified factor or entity.
-
E.
speedupType
Indicates the kind or category of performance improvement achieved relative to a baseline.
- 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_69f348e70d188190b4637c5509f81274 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b0d21dd08190a9883ff71c94c71c |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6afeaaef88190aefa97e83f8db906 |
completed | May 3, 2026, 2:16 a.m. |
Created at: April 30, 2026, 11:43 p.m.