Triple
T3616442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M60 |
E76610
|
entity |
| Predicate | hasVariableSpeedSections |
P48528
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [M60, hasVariableSpeedSections, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVariableSpeedSections Context triple: [M60, hasVariableSpeedSections, yes]
-
A.
hasVariableSpeedLimits
chosen
Indicates that the subject is associated with speed limits that can change depending on conditions, time, or location.
-
B.
hasUnrestrictedSpeedSection
Indicates that a route or roadway segment includes a section where no specific maximum speed limit is imposed.
-
C.
hasSectionWithSpeedLimit
Indicates that an entity includes a segment or portion where a specific speed limit is in effect.
-
D.
hasScenicSections
Indicates that a route, path, or area contains segments that are visually attractive or offer notable scenic views.
-
E.
hasExpresswaySection
Indicates that an entity includes, contains, or is associated with a specific section or segment of an expressway.
- 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_69ad85dae2fc81908d1ceadbc6af0089 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc27c98088190a493c9eddf6b206a |
completed | March 8, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69adb83f1e4c8190ab501c1c05b14c08 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.